You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wsrp4j-dev@portals.apache.org by dl...@apache.org on 2006/12/15 00:21:48 UTC

svn commit: r487386 - /portals/wsrp4j/trunk/README.txt

Author: dlouzan
Date: Thu Dec 14 15:21:47 2006
New Revision: 487386

URL: http://svn.apache.org/viewvc?view=rev&rev=487386
Log:
Misc formatting and corrected some typos.

Modified:
    portals/wsrp4j/trunk/README.txt

Modified: portals/wsrp4j/trunk/README.txt
URL: http://svn.apache.org/viewvc/portals/wsrp4j/trunk/README.txt?view=diff&rev=487386&r1=487385&r2=487386
==============================================================================
--- portals/wsrp4j/trunk/README.txt (original)
+++ portals/wsrp4j/trunk/README.txt Thu Dec 14 15:21:47 2006
@@ -129,7 +129,7 @@
 
      - Unpack the distribution on some directory (like ~/local):
        $ cd ~/local
-       $ tar xvzf ~/dowloads/apache-tomcat-5.5.16.tar.gz
+       $ tar xvzf ~/downloads/apache-tomcat-5.5.16.tar.gz
 
      - Check that your distribution is working properly by executing Tomcat:
        $ cd ~/local/apache-tomcat-5.5.16/bin
@@ -208,10 +208,10 @@
    - Copy build.properties.sample to build.properties.
 
    - Edit build.properties and enter your Tomcat installation dir for both 
-     Proxyportlet and Producer. These parameters will setup the location of your 
-     installation in WSRP4J configuration files, but won't actually deploy your
-     applications to tomcat, you have to manually add them later. For a basic
-     installation, set the same path on both variables.
+     Proxyportlet and Producer. These parameters will setup the location of
+     your installation in WSRP4J configuration files, but won't actually deploy
+     your applications to tomcat, you have to manually add them later. For a 
+     basic installation, set the same path on both variables.
 
    - Run Maven and generate packages for each module:
      $ mvn package
@@ -259,7 +259,7 @@
      enabling XML indentation.
 
    - Point your browser again to PlutoPortal and on the menu on the left select
-     the WSRP4J Producer you deployed before.
+     the WSRP4J Proxyportlet you deployed before.
 
    - Enjoy your WSRP portlets :-)
 
@@ -272,12 +272,13 @@
    new remote portlets to proxyportlet. Unfortunately, the default PlutoPortal
    distribution does not support dynamic reloading of portlet.xml contents, that
    is, that file will only be processed once when you deploy proxyportlet for
-   the first time, and later modifications on it won't be automatically
+   the first time, and subsequent modifications on it won't be automatically
    deployed. You can manually add new modifications by stopping Tomcat and
    executing:
    $ cd $PLUTO_HOME
+   $ export MAVEN_HOME=~/local/maven-1.0.2; export PATH=$MAVEN_HOME/bin:$PATH
    $ maven deploy -Ddeploy=$CATALINA_HOME/webapps/wsrp4j-proxyportlet
-   Then start Tomcat and your new wsrp portlets will be deployed on
+   Then restart Tomcat and your new wsrp portlets will be deployed on
    proxyportlet ConfigPortlet.
 
    Other portals (like Apache Jetspeed) do support dynamic reloading of
@@ -287,19 +288,8 @@
    then edit commons/pom.xml and uncomment the antrun-plugin in the <plugins>
    section, then rebuild the project. The Axis-generated sources will be located
    in directory commons/target/generated-sources/wsdl. This files won't be used
-   for actually building the libraries, the ones used are below
+   for actually building the libraries, the ones used are under
    commons/src/java/. See commons/src/wsdl/README.txt for more details.
-
-   The proxyportlet and producer wars are located on their respective
-   target directories (consumer-proxyportlet/target/wsrp4j-proxyportlet.war and
-   producer/target/wsrp4j-producer.war).
-
-   For deploying the proxyportlet, just install Pluto 1.0.1 with PlutoPortal and 
-   use the admin portlet bundled with PlutoPortal to deploy
-   wsrp4j-proxyportlet.war. The default producer configuration files supplied
-   with proxyportlet assume you have started the corresponding tunnel script
-   from tools/ directory. This tunnel tool will allow you to view the wsrp 
-   messages exchanged between the consumer and the producer.
 
 6. Known problems
    --------------