You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by jm...@apache.org on 2004/06/17 16:22:46 UTC

cvs commit: ws-site/targets/wsrp4j/arch producer.html consumer.html consumer.pdf

jmacna      2004/06/17 07:22:46

  Modified:    targets/wsrp4j installation.pdf installation.html
               targets/wsrp4j/arch producer.html consumer.html consumer.pdf
  Added:       targets/wsrp4j/images WSRPArch4.png WSRPArch3.png
  Log:
  Fixed architecture drawings to be smaller and consistent color scheme.
  
  Revision  Changes    Path
  1.1                  ws-site/targets/wsrp4j/images/WSRPArch4.png
  
  	<<Binary file>>
  
  
  1.1                  ws-site/targets/wsrp4j/images/WSRPArch3.png
  
  	<<Binary file>>
  
  
  1.2       +25 -17    ws-site/targets/wsrp4j/installation.pdf
  
  	<<Binary file>>
  
  
  1.6       +21 -2     ws-site/targets/wsrp4j/installation.html
  
  Index: installation.html
  ===================================================================
  RCS file: /home/cvs/ws-site/targets/wsrp4j/installation.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- installation.html	3 Mar 2004 19:51:21 -0000	1.5
  +++ installation.html	17 Jun 2004 14:22:46 -0000	1.6
  @@ -204,6 +204,26 @@
       
   <ol>
       
  +<li>Configure the location of your Tomcat installation.
  +      <p>
  +        Currently you have to do this in several locations. In each
  +        location you have to copy a file called <em>build.properties.example</em>
  +        to <em>build.properties</em> and correct the path to the
  +        Tomcat directory in the newly created file.  The file locations are:
  +      </p>
  +      
  +<ul>
  +        
  +<li>In the ws-wsrp4j/build directory,</li>
  +        
  +<li>in the ws-wsrp4j/portlets/proxyportlet directory and</li>
  +        
  +<li>in the ws-wsrp4j/portlets/wsrptest directory.</li>
  +      
  +</ul>
  +    
  +</li>
  +    
   <li>Change your working directory to the ws-wsrp4j/build direcory.</li>
       
   <li>Run the install-swing-consumer script (either sh or bat).
  @@ -220,8 +240,7 @@
       
   <li>Run the install-provider-pluto script (either sh or bat).
         <p>
  -      This script prompts for the Tomcat installation directory. The
  -      Pluto provider is installed as a webapp in the Tomcat webapps
  +      The Pluto provider is installed as a webapp in the Tomcat webapps
         directory. A sample portlet is also installed.
         </p>
         
  
  
  
  1.5       +1 -1      ws-site/targets/wsrp4j/arch/producer.html
  
  Index: producer.html
  ===================================================================
  RCS file: /home/cvs/ws-site/targets/wsrp4j/arch/producer.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- producer.html	3 Mar 2004 19:53:21 -0000	1.4
  +++ producer.html	17 Jun 2004 14:22:46 -0000	1.5
  @@ -122,7 +122,7 @@
       </p>
       
   <div align="center">
  -<img class="figure" alt="WSRP Producer Architecture" src="../images/producer_architecture.jpg"></div>
  +<img class="figure" alt="WSRP Producer Architecture" src="../images/WSRPArch3.png"></div>
       
   <div class="h3">
   <h3>WSRPEngine</h3>
  
  
  
  1.5       +3 -8      ws-site/targets/wsrp4j/arch/consumer.html
  
  Index: consumer.html
  ===================================================================
  RCS file: /home/cvs/ws-site/targets/wsrp4j/arch/consumer.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- consumer.html	3 Mar 2004 19:53:21 -0000	1.4
  +++ consumer.html	17 Jun 2004 14:22:46 -0000	1.5
  @@ -121,7 +121,7 @@
       </p>
       
   <div align="center">
  -<img class="figure" alt="Consumer Architecture" src="../images/consumer_architecture.jpg"></div>
  +<img class="figure" alt="Consumer Architecture" src="../images/WSRPArch4.png"></div>
       
   <div class="h3">
   <h3>Protocol Handler</h3>
  @@ -132,7 +132,7 @@
         implements the consuming portal and the browser functionality. It
         aggregates the integrated WSRP portlets and forwards all
         invocations together with relevant context and request information
  -      to the remote WSRP service. The Swing consumer thereby uses the
  +      to the remote WSRP service. The SwingConsumer thereby uses the
         ConsumerEnvironment to collect all data required for a WSRP call.
         </p>
       
  @@ -155,15 +155,10 @@
         The PortletDriver is the task oriented abstraction of the
         generated WSRP stubs for markup and action invocation.
         </p>
  -      
  -<p>
  -      The PortletDriver is the task oriented abstraction of the
  -      generated WSRP stubs for markup and action invocation.
  -      </p>
       
       
   <div class="h3">
  -<h3>WSRP service (stubs) () </h3>
  +<h3>WSRP Stubs </h3>
   </div>
         
   <p>
  
  
  
  1.2       +42 -42    ws-site/targets/wsrp4j/arch/consumer.pdf
  
  	<<Binary file>>