Hi,
I was wondering if the release of Commons Chain 1.0 will enable a "Best Available" release of Struts with struts-chain? If not, how stable is the COR stuff in Struts?
The struts-chain was working just fine against pre-1.0 releases of Struts Chain. If you're interested, there's no reason to wait. It will be longer before you can download a nightly build of Struts which uses the Chain request processor, but work on that was mostly waiting for the 1.0 release (and for time, which unfortunately I've had a short supply of, and this time of year, it will continue that way.)
I have a few pending questions on the dev list that I may need to re-raise about a few implementation details, but now that 1.0 is fully released, I do hope to begin making changes to the core code base to use commons-chain and the Composable Request Processor. I don't see the point of just merging struts-chain into the 'core' project and cutting a release; rather, we'll want to obsolete the PlugIn which configures the command catalogs in struts-chain in favor of direct support in the ActionServlet. I am also inclined to package the set of commands which provide legacy Struts support as a separate JAR, rather than pushing a few dozen classes into the core which in some sense are legacy bound. (Whether there's consensus on that is one of the questions to re-raise on the dev list.)
I've been using struts-chain in a production project for close to a year now (including original development time). We flushed a few bugs out along the way, but it's fundamentally stable with Struts 1.2.x.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
