One thing that bothers me is that RequestProcessor is not an interface which leads to the Tiles situation. If it were an interface, you could implement your one method and delegate the rest to the TilesRequestProcessor or any number of other processors.
IMO, RequestProcessor should be an interface in Struts 2.0 to allow the composition you're looking for.
If you're really composing, would it make more sense to have the composition happen in a config file? Unless I misunderstand you, there's still a fair bit of work required to implement a RequestProcessor interface by writing an implementation class that calls on delegates. There's no reason you couldn't do both, though.
I was thinking something like this:
<controller>
<request-processor className="com.foo.bar.MyRequestProcessor">
<delegate stage="actionForm" type="com.foo.bar.MyFormProcessor" />
<delegate stage="forwardConfig" type="org.apache.struts.tiles.TilesForwardConfigProcessor" />
</request-processor>
</controller>
Of course, this is a substantial change to the DTD, but it might still fit into Struts 1.2....
Joe
--
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "If nature worked that way, the universe would crash all the time." --Jaron Lanier
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
