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 2007/01/12 20:35:19 UTC

svn commit: r495700 - /portals/wsrp4j/trunk/WHATWHERE.txt

Author: dlouzan
Date: Fri Jan 12 11:35:18 2007
New Revision: 495700

URL: http://svn.apache.org/viewvc?view=rev&rev=495700
Log:
Corrected some errors on the docs.

Modified:
    portals/wsrp4j/trunk/WHATWHERE.txt

Modified: portals/wsrp4j/trunk/WHATWHERE.txt
URL: http://svn.apache.org/viewvc/portals/wsrp4j/trunk/WHATWHERE.txt?view=diff&rev=495700&r1=495699&r2=495700
==============================================================================
--- portals/wsrp4j/trunk/WHATWHERE.txt (original)
+++ portals/wsrp4j/trunk/WHATWHERE.txt Fri Jan 12 11:35:18 2007
@@ -42,27 +42,27 @@
     Xml mapping persistence implementation. Implements the persistent packages
     included on commons, storing all required persistent information needed by
     consumers and producers as xml files.
-  	Depends on commons, commons-producer and commons-consumer.
+    Depends on commons, commons-producer and commons-consumer.
 
 consumer-proxyportlet/
     Jsr-168 portlet wsrp consumer implementation. Implements a jsr-168-compliant
     portlet aplication pluggable on any portal server which supports the jsr-168
     standard for consuming remote wsrp portlets.
-    Depends on commons, commons-consumer and persistence-xml.
+    Depends on commons and commons-consumer.
 
 consumer-swingconsumer/
- 	Java Swing application wsrp consumer implementation. Not currently actively
+    Java Swing application wsrp consumer implementation. Not currently actively
     developed.
- 	Depends on commons, commons-consumer and persistence-xml.
+    Depends on commons and commons-consumer.
 
 producer/
- 	Axis-based producer implementation. Uses an axis servlet for receiving the
+    Axis-based producer implementation. Uses an axis servlet for receiving the
     requests and forwards them to a provider backend implementation. The
     producer code is generic and uses the provider interfaces for serving the
     actual markup returned by the portlets. The  default provider implementation
     is based on pluto-portal, this way the portlets served by producer are
     standard jsr-168 portlets rendered by pluto-portal.
- 	Depends on commons, commons-producer and persistence-xml.
+    Depends on commons and commons-producer.
 
 testportlet/
     Jsr-168 test portlet. A jsr-168 portlet used to test both the consumer and