I'd like to use Avalon for the lifecycle management of Struts Action and ActionForm objects. But it seems that in order to do so, the RequestProcessor class would need to be replaced, or at least the processActionForm() and processActionCreate() methods, in order to perform the lifecycle management upon object creation. Is this desirable? I think I would only be using the LogEnabled and Serviceable interfaces for these objects - to get the correct log to use and to be able to use services from my Actions and ActionForms.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Subclassing the RequestProcessor would indeed make sense for something like this.
For future versions, we're experimenting with dividing the RequestProcessor class into discrete elements using the Chain of Responsibility pattern (see the contrib/struts-chain sources in the Struts CVS repository, and commons-chain in the Jakarta Commons Sandbox). In that sort of a world, you would just customize the corresponding elements of the chain to accomplish specializations like this.
Please report back on your progress -- I'm interested in seeing the different approaches people take to integrating IoC and SOA type architectures into Struts.
Craig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
