On 10/9/05, Legolas Woodland <[EMAIL PROTECTED]> wrote: > Hi > Thank you for reading my mail. > What is new in struts 1.3 ?
The codebase that would become Struts 1.3.x is available as our nightly build. A copy of the release notes is available here: * http://wiki.apache.org/struts/StrutsClassicRelease130Notes > will already made application based on struts > 1.1 works with new Struts ? We retain full backwardly compatability between minor releases, using a standard deprecate/release/remove/release cycle. If you stay on track with the latest General Availability release, and address all the deprecation warnings, then the application should be compatible with the next minor release. Since there were deprecations between 1.1 and 1.2, you will need to address those before moving on to 1.3. But, if the and 1.1 and 1.2 deprecations are addressed, then, yes, your application should work with 1.3 "out of the box". > is it based on shale ? No. Shale is a distinct product for teams that want to move from an "action-centric" architecture to an "event-centric" architectureusing JSF. There's no clear migration path between the two for non-trivial applications, and so we doubt that JSR or Shale could be supported within the Struts Classic 1.x series. (Since it would break backward compatability.) > does tag library grown ? Not really. The Struts Taglib subproject is focussed on supporting just the HTML 4.01 specification, which doesn't leave much room for growth. For more advanced taglibs, I would suggest Struts Layout, DisplayTag, and JavaWebAprts. * http://struts.application-servers.com/struts-layout/ * http://displaytag.sourceforge.net/ * http://wiki.apache.org/struts/AjaxStruts > Thank you > -- HTH, Ted. http://www.husted.com/poe/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
