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 jm...@apache.org on 2004/06/17 16:26:05 UTC
cvs commit: ws-wsrp4j/site/src/documentation/content/xdocs/arch consumer.xml producer.xml
jmacna 2004/06/17 07:26:05
Modified: site/src/documentation/content/xdocs installation.xml
site/src/documentation/content/xdocs/arch consumer.xml
producer.xml
Added: site/src/documentation/content/xdocs/images WSRPArch4.png
objectModel.png WSRPArch3.png
Log:
Fixed up architecture drawings
Revision Changes Path
1.1 ws-wsrp4j/site/src/documentation/content/xdocs/images/WSRPArch4.png
<<Binary file>>
1.1 ws-wsrp4j/site/src/documentation/content/xdocs/images/objectModel.png
<<Binary file>>
1.1 ws-wsrp4j/site/src/documentation/content/xdocs/images/WSRPArch3.png
<<Binary file>>
1.3 +1 -1 ws-wsrp4j/site/src/documentation/content/xdocs/installation.xml
Index: installation.xml
===================================================================
RCS file: /home/cvs/ws-wsrp4j/site/src/documentation/content/xdocs/installation.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- installation.xml 9 Jun 2004 13:52:40 -0000 1.2
+++ installation.xml 17 Jun 2004 14:26:05 -0000 1.3
@@ -21,7 +21,7 @@
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:
+ Tomcat directory in the newly created file. The file locations are:
</p>
<ul>
<li>In the ws-wsrp4j/build directory,</li>
1.2 +3 -7 ws-wsrp4j/site/src/documentation/content/xdocs/arch/consumer.xml
Index: consumer.xml
===================================================================
RCS file: /home/cvs/ws-wsrp4j/site/src/documentation/content/xdocs/arch/consumer.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- consumer.xml 13 Nov 2003 01:04:29 -0000 1.1
+++ consumer.xml 17 Jun 2004 14:26:05 -0000 1.2
@@ -12,14 +12,14 @@
hiding the portal's object model and thus gaining independence of
changes in the portal implementation or design.
</p>
- <figure src="../images/consumer_architecture.jpg" alt="Consumer Architecture"/>
+ <figure src="../images/WSRPArch4.png" alt="Consumer Architecture"/>
<section><title>Protocol Handler</title>
<p>
The Protocol Handler is a standalone Swing based application that
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>
</section>
@@ -34,12 +34,8 @@
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>
</section>
- <section><title>WSRP service (stubs) () </title>
+ <section><title>WSRP Stubs </title>
<p>
The stubs generated by the axis SOAP implementation. The stubs are
also implementing the cookie handling - for more details see
1.2 +1 -1 ws-wsrp4j/site/src/documentation/content/xdocs/arch/producer.xml
Index: producer.xml
===================================================================
RCS file: /home/cvs/ws-wsrp4j/site/src/documentation/content/xdocs/arch/producer.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- producer.xml 13 Nov 2003 01:04:29 -0000 1.1
+++ producer.xml 17 Jun 2004 14:26:05 -0000 1.2
@@ -13,7 +13,7 @@
and thus gaining independence of changes in the environment's
implementation or design.
</p>
- <figure src="../images/producer_architecture.jpg" alt="WSRP Producer Architecture"/>
+ <figure src="../images/WSRPArch3.png" alt="WSRP Producer Architecture"/>
<section><title>WSRPEngine</title>
<p>
The WSRPEngine is the WSRP implementation endpoint. This class