cvs commit: jakarta-struts/contrib/struts-jericho README.txt

2003-12-18 Thread husted 
husted  2003/12/18 05:21:13

  Modified:contrib/struts-jericho README.txt
  Log:
  Clarificatioins and additional items for consideration.
  
  Revision  ChangesPath
  1.3   +1 -1  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.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- README.txt18 Dec 2003 13:19:59 -  1.2
  +++ README.txt18 Dec 2003 13:21:13 -  1.3
  @@ -54,6 +54,6 @@
   
   * Integrate Tiles definitions into core configuration.
   
  -* Adopt Struts Menu as an standard option, like Validator and Tiles.
  +* Adopt Struts Workflow and Struts Menu as standard options, like Validator and 
Tiles.
   
   ###
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-struts/contrib/struts-jericho README.txt

2003-12-18 Thread husted 
husted  2003/12/18 05:22:59

  Modified:contrib/struts-jericho README.txt
  Log:
  Clarificatioins and additional items for consideration.
  
  Revision  ChangesPath
  1.4   +2 -2  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.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- README.txt18 Dec 2003 13:21:13 -  1.3
  +++ README.txt18 Dec 2003 13:22:59 -  1.4
  @@ -42,7 +42,7 @@
   
   -Also under consideration-
   
  -* Services_framework. Utilize Sprint IoC, HiveMind, Avalon, orPico, et cetera, to 
configure services.
  +* Services framework. Utilize Spring IoC, HiveMind, Avalon, orPico, et cetera, to 
configure services.
   
   * Configuration testing. Integrate utility of Struts TestCase, ideally configured 
from an XML configuration (a la Canoo Webtest).
   
  @@ -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.
   
  -* Merge 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 knowns about a form to be configured in one place.
   
   * Integrate Tiles definitions into core configuration.
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-struts/contrib/struts-jericho README.txt

2003-12-18 Thread husted 
husted  2003/12/18 06:10:07

  Modified:contrib/struts-jericho README.txt
  Log:
  Clarifications and additional items for consideration.
  
  Revision  ChangesPath
  1.5   +2 -0  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.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- README.txt18 Dec 2003 13:22:59 -  1.4
  +++ README.txt18 Dec 2003 14:10:07 -  1.5
  @@ -56,4 +56,6 @@
   
   * Adopt Struts Workflow and Struts Menu as standard options, like Validator and 
Tiles.
   
  +* Utilize JodaBeans http://www.joda.org/ as a foundation class for core 
components.
  +
   ###
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-struts/contrib/struts-jericho README.txt

2003-12-18 Thread husted 
husted  2003/12/18 09:26:33

  Modified:contrib/struts-jericho README.txt
  Log:
  Clarifications and additional items for consideration.
  
  Revision  ChangesPath
  1.6   +2 -0  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.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- README.txt18 Dec 2003 14:10:07 -  1.5
  +++ README.txt18 Dec 2003 17:26:33 -  1.6
  @@ -58,4 +58,6 @@
   
   * 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.
  +
   ###
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-struts/contrib/struts-jericho README.txt

2003-12-18 Thread martinc 
martinc 2003/12/18 10:14:36

  Modified:contrib/struts-jericho README.txt
  Log:
  Add Cornerstone (from Jetspeed 2) to the list of frameworks to consider.
  
  Revision  ChangesPath
  1.7   +1 -1  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.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- README.txt18 Dec 2003 17:26:33 -  1.6
  +++ README.txt18 Dec 2003 18:14:36 -  1.7
  @@ -42,7 +42,7 @@
   
   -Also under consideration-
   
  -* Services framework. Utilize Spring IoC, HiveMind, Avalon, orPico, et cetera, to 
configure services.
  +* Services framework. Utilize Spring IoC, HiveMind, Avalon, Pico, Cornerstone, et 
cetera, to configure services.
   
   * Configuration testing. Integrate utility of Struts TestCase, ideally configured 
from an XML configuration (a la Canoo Webtest).
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-struts/contrib/struts-jericho README.txt OVERVIEW.txt

2003-12-18 Thread husted 
husted  2003/12/18 10:26:50

  Modified:contrib/struts-jericho README.txt OVERVIEW.txt
  Log:
  Mention SOAP.
  
  Revision  ChangesPath
  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.txt18 Dec 2003 18:14:36 -  1.7
  +++ README.txt18 Dec 2003 18:26:50 -  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 -  1.2
  +++ OVERVIEW.txt  18 Dec 2003 18:26:50 -  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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-struts/contrib/struts-jericho README.txt

2003-12-18 Thread husted 
husted  2003/12/18 17:05:51

  Modified:contrib/struts-jericho README.txt
  Log:
  Additional item for consideration.
  
  Revision  ChangesPath
  1.9   +2 -0  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.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- README.txt18 Dec 2003 18:26:50 -  1.8
  +++ README.txt19 Dec 2003 01:05:50 -  1.9
  @@ -60,4 +60,6 @@
   
   * Load all configuration defaults form a core.properties file so that less is 
hardcoded, including a PlugIn class to bootstrap loading the core configuraiton.
   
  +* 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-struts/contrib/struts-jericho README.txt project.properties project.xml

2003-12-17 Thread husted 
husted  2003/12/17 12:49:28

  Added:   contrib/struts-jericho README.txt project.properties
project.xml
  Log:
  Create whiteboard directory for Struts-Jericho, a working proposal for Struts 2.x.
  
  Revision  ChangesPath
  1.1  jakarta-struts/contrib/struts-jericho/README.txt
  
  Index: README.txt
  ===
  Jericho is a whiteboard proposal describing one possible implementation of Struts 
2.x.
  
  Since Struts 2.x is slated as a revolution, the Apache practice is to assign a 
codename to a proposal until the Community comes to a consensus.
  
  This proposal is called Jericho since it tries to tear-down the walls within the 
Struts architecture. Jericho proposes to open-up Struts by
  
  * Declaring interfaces for all core components.
  
  * 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.
  
  * Providing additional extension points from core components so that the Inversion 
of Control pattern is fully realized.
  
  * Providing POJO signatures that encapsulate HTTP classes so that applications can 
be freed of HTTP semantics, if so desired.
  
  * Retain optional access to HTTP objects so that applications can be free to do 
whatever they need to do.
  
  -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.
  
  _DTD._ The Jericho Configuration file (DTD) builds on the best aspects of the Struts 
1.2 DTD. The elements are different but still similar. Our goal is to allow a tool, 
such as a XLST processor, to migrate a Struts 1.2 DTD to Struts Jericho.
  
  A second alternative to explore is to provide an alternate configuration loader that 
would map the Struts 1.2 elements to Struts Jericho objects at initialization.
  
  _Base Classes._ New base classes for Struts 1.2.x ActionForms and Actions are to 
provided. These classes will provide the Struts 1.2.x behavior but also implement the 
Struts Jericho interfaces, so that the framework can use them interchangeably.
  
  These same techniques may be applied to provide adaptors for other frameworks, so as 
to make Struts Jericho available to the widest community possible.
  
  ###
  
  
  1.1  jakarta-struts/contrib/struts-jericho/project.properties
  
  Index: project.properties
  ===
  # ---
  # P R O J E C T  P R O P E R T I E S
  # ---
  
  compile.debug = on
  compile.optimize = off
  compile.deprecation = off
  
  maven.linkcheck.enable=true 
  
  # documentation properties
  maven.xdoc.date=left
  maven.xdoc.version=${pom.currentVersion}
  maven.xdoc.developmentProcessUrl=http://jakarta.apache.org/struts/status.html
  
  
  
  1.1  jakarta-struts/contrib/struts-jericho/project.xml
  
  Index: project.xml
  ===
  ?xml version=1.0 encoding=UTF-8?
  
  project
extend../project.xml/extend
nameJericho/name
idstruts-jericho/id
currentVersion0.1-dev/currentVersion
inceptionYear2003/inceptionYear
shortDescriptionStruts Jericho 2.x Whiteboard/shortDescription
description
Jericho is a whiteboard proposal describing one possible implementation of 
Struts 2.x.
Since Struts 2.x is slated as a revolution, the Apache practice is to assign 
a codename to a proposal
until the Community comes to a consensus.
This proposal is called Jericho since it tries to tear-down the walls within 
the Struts architecture.
/description
developers
  developer
nameTed Husted/name
idhusted/id
email[EMAIL PROTECTED]/email
organization/organization
  /developer
/developers
  
build
  unitTest
includes
  include**/*Test.java/include
/includes
  /unitTest
/build
  
  /project
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]