You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by hu...@apache.org on 2003/12/18 19:26:50 UTC
cvs commit: jakarta-struts/contrib/struts-jericho README.txt OVERVIEW.txt
husted 2003/12/18 10:26:50
Modified: contrib/struts-jericho README.txt OVERVIEW.txt
Log:
Mention SOAP.
Revision Changes Path
1.8 +3 -3 jakarta-struts/contrib/struts-jericho/README.txt
Index: README.txt
===================================================================
RCS file: /home/cvs/jakarta-struts/contrib/struts-jericho/README.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- README.txt 18 Dec 2003 18:14:36 -0000 1.7
+++ README.txt 18 Dec 2003 18:26:50 -0000 1.8
@@ -12,7 +12,7 @@
* Providing additional extension points from core components so that the "Inversion of Control" pattern is fully realized. (e.g., a populate method for the FormHandler.)
-* Providing "POJO" signatures that encapsulate servlet/portlet behavior so that applications can be freed of servlet/portlet semantics, if so desired. This strategy would also be applied to optional packages like Validator and Tiles.
+* Providing "POJO" signatures that encapsulate servlet/portlet/soap behavior so that applications can be freed of servlet/portlet/soap semantics, if so desired. This strategy would also be applied to optional packages like Validator and Tiles.
* Retain optional access to servlet/portlet objects so that applications can be free to do whatever they need to do.
@@ -36,9 +36,9 @@
A second alternative might be to provide an alternate configuration loader that would map the Struts 1.2 elements to Struts Jericho objects at initialization.
--Servlet/Portlet/Mock support-
+-Servlet/Portlet/Soap/Mock support-
-Core components will implement signatures that reference a StrutsContext. Implementations of this interface can be backed by servlet, portlet, or mock implementations as needed.
+Core components will implement signatures that reference a StrutsContext. Implementations of this interface can be backed by servlet, portlet, soap, or mock implementations as needed.
-Also under consideration-
1.3 +1 -1 jakarta-struts/contrib/struts-jericho/OVERVIEW.txt
Index: OVERVIEW.txt
===================================================================
RCS file: /home/cvs/jakarta-struts/contrib/struts-jericho/OVERVIEW.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- OVERVIEW.txt 18 Dec 2003 17:58:34 -0000 1.2
+++ OVERVIEW.txt 18 Dec 2003 18:26:50 -0000 1.3
@@ -6,7 +6,7 @@
Command Context
* Extends CoR Context to encapsulate framework members needed to process request and render response
-Request Adapter (module, portlet, mock)
+Request Adapter (servlet module, portlet, SOAP, mock)
* Receives request from container (or TestRunner)
* Normalizes request path (masks pattern registered with container)
* Creates context to wrap request and response objects
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org