On a personal note, I look at Struts Chain and I wonder, should I use Struts Actions or simply make my own chain command to execute chains based upon the action path? Which is better and which is the "path", I don't know. Maybe someone can answer that question for future versions of Struts.
Since we'll be going to some lengths to be backwards compatible with traditional struts-config.xml files, I don't think you have to worry about Action being deprecated. Everyone recognizes the similarity between Action and Command, but there's no rush to throw out all of our Struts traditions either. For example, the <action> element in struts-config actually affects much more than just the execution of the action. The mapping actually governs more than half of the commands in the servlet-standard sub-chain (all those to do with form population, and validation as well as basic action execution.)
I know it took me rather a while to feel like I understood the chain, because it seems so abstract. I suspect others will have the same experience. Insofar as this is true, the chain may be invisible to a good proportion of struts users, as the current RequestProcessor is today. I wouldn't say it will be "experts-only" territory, but it might even be something left out of (or glossed over in) the typical Struts 1.3 book.
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]
