At some point, it would also be nice to extract the taglibs into a separate subproject, since in 1.3.x we agreed that they would not be part of the "core".
Ditto for the struts-examples. These are suppose to go into an "apps" subproject. I'd also be in favor of an "extras" subproject, to distribute what we now have under "actions" and "plugins". Each subproject (including core) could start out with a 1.0.0 release. We could then bundle the latest GA releases for each subproject into a "Struts 1.3.0 distribution" (a la Linux). -Ted. On Thu, 16 Dec 2004 21:47:53 -0800, Don Brown wrote: > Who is working on bringing Struts chain into Struts core? If no > one, I wouldn't mind doing the integration. > > I'm thinking about using the ComposableRequestProcessor to keep as > much backwards compatibility as possible. The changes I'm > proposing by layer: > > web.xml > - A "chainConfig" parameter to override default catalog. If none > specified, a default chain config will be loaded from the Struts > jar. - A "chainCommand" parameter to specify the command to execute > if none specified in modules (optional) > > struts-config.xml > - The default request processor class would now be > ComposableRequestProcessor, but the legacy ones would still be > available (deprecated) > - The controller would have additional optional attributes: - > "chainConfig" - path of chain config to override default chain > catalog. Cannot be used if "catalog" is specified. > - "catalog" - name of servlet context attribute to locate catalog > for this module. Cannot be used of "chainConfig" is used. - > "command" - name of command to execute. Overrides default chain > command name. - Remove the need for the chain plugin > > Of course, if someone is already doing the integration, ignore > this. Otherwise, comments appreciated. I'll target the integration > Sunday or Monday if I don't hear different. > > Don > > > -------------------------------------------------------------------- > - To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
