On 7/17/06, Adam Hardy <[EMAIL PROTECTED]> wrote:
Is 1.3.5 beta or alpha?
Neither. The grade will be assigned after voting in about a week. See dev list for details. 1.3.5 is the fifth build since 1.3.0 and is being expected to make a GA grade. At least that is the intention of those who are putting their time into preparing the build and fixing the glitches.
Also, where should I be looking for docs of 1.3.x feature enhancements such as chaining?
The RequestProcessor side of chaining is explained in the current user's guide [1], see 4.2.1 and 4.2.2. Also see WhyChain page in the wiki [2] and the links on the bottom of it. For new dispatch action see this page [3]. I would appreciate if you looked at "Developing Components with Struts" page [4] and shared your opinion on whether such a feature would be useful. Caution, this is not a feature of 1.3.5 and it is not even accepted in future versions yet, this is just a proposal. Do you think that Struts components should support JSR-168 portlet spec out of the box?
"In fact, in Struts 1.3, some of the same "convention of configuration" practices are applied in the configuration files: you can define mapping conventions in struts-config.xml without having to define every single action." (from Patrick Lightbody)
Um, I don't know anything about that. I presume Patrick was talking about Struts 2.0 based on Webwork. [1]http://struts.apache.org/1.x/userGuide/building_controller.html#request_processor [2]http://wiki.apache.org/struts/WhyChain [3]http://wiki.apache.org/struts/EventActionDispatcher [4]http://wiki.apache.org/struts/StrutsManualActionWebComponent Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
