You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by jm...@apache.org on 2004/09/02 14:41:52 UTC
cvs commit: jakarta-struts/contrib/struts-jericho OVERVIEW.txt README.txt
jmitchell 2004/09/02 05:41:52
Modified: contrib/struts-jericho OVERVIEW.txt README.txt
Log:
quick spell-check
Revision Changes Path
1.5 +2 -2 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.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- OVERVIEW.txt 19 Dec 2003 02:31:05 -0000 1.4
+++ OVERVIEW.txt 2 Sep 2004 12:41:52 -0000 1.5
@@ -1,7 +1,7 @@
-COMPONENT OVERVIEW-
Configuration registry
-* At initialiation, each request adapter (servlet, filter, et cetera), adds its configuration to a single registry at a global location under a unique key.
+* At initialization, each request adapter (servlet, filter, et cetera), adds its configuration to a single registry at a global location under a unique key.
Command Context
* Extends CoR Context to encapsulate framework members needed to process request and render response
@@ -37,7 +37,7 @@
* Invalid
* MappingHandler
* Command | Script
- * Invoke buiness logic
+ * Invoke business logic
* Affect context state
* Identify resource to render response
* Location
1.10 +6 -6 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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- README.txt 19 Dec 2003 01:05:50 -0000 1.9
+++ README.txt 2 Sep 2004 12:41:52 -0000 1.10
@@ -8,7 +8,7 @@
* Providing working base implementations for all core components.
-* Encapsulating alll path references within "Location" objects (fka ActionForwards)and referring only to Locations from all other objects.
+* Encapsulating all path references within "Location" objects (aka ActionForwards)and referring only to Locations from all other objects.
* 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.)
@@ -16,13 +16,13 @@
* Retain optional access to servlet/portlet objects so that applications can be free to do whatever they need to do.
--Backward Compatability-
+-Backward Compatibility-
-Jericho is a revolution and backward compatability with prior versions of Struts is not the prime consideration. However, care is being taken to create a clear migration path, where practible, so that Jericho is available to the widest community possible.
+Jericho is a revolution and backward compatibility with prior versions of Struts is not the prime consideration. However, care is being taken to create a clear migration path, where practical, so that Jericho is available to the widest community possible.
-Taglibs/Tools-
-JSP taglibs and other presention tools will be packaged separately from the core controller classes. Tags and tools can access the framework through a StrutsContext object passed through the request, rather than searching through the servlet or portlet contexts.
+JSP taglibs and other presentation tools will be packaged separately from the core controller classes. Tags and tools can access the framework through a StrutsContext object passed through the request, rather than searching through the servlet or portlet contexts.
-ActionForms/Actions, et al-
@@ -50,7 +50,7 @@
* Utilize protocols in resource paths. An mapped path would look like "mapping://foo" or a tiles forward would be "tiles://tilesdef" This would make it easy to plug in handlers to support different presentation engines. If no protocol is specified, the path is handled as usual.
-* Combine form-bean and validator-form configurations. A single element would allow everything Struts knowns about a form to be configured in one place.
+* Combine form-bean and validator-form configurations. A single element would allow everything Struts knows about a form to be configured in one place.
* Integrate Tiles definitions into core configuration.
@@ -58,7 +58,7 @@
* Utilize JodaBeans <http://www.joda.org/> as a foundation class for core components.
-* Load all configuration defaults form a core.properties file so that less is hardcoded, including a PlugIn class to bootstrap loading the core configuraiton.
+* Load all configuration defaults form a core.properties file so that less is hardcoded, including a PlugIn class to bootstrap loading the core configuration.
* Ensure that all framework objects in 2.0 have consistent factory-based mechanisms to instantiate instances. <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15604>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org