I've looked at 1.3 and the Chain stuff, but not actually tried it out. However the original RequestProcessor is still there and presumably still works. The default RequestProcessor is now the chain ComposableRequestProcessor, so to use the original one would have to be configured. No one (to my knowledge) has said it should be removed, so theres nothing to stop it being maintained/enhanced and if Struts continues to ship with both no need (IMO) for a fork. Having said that if ComposbaleRequestProcessor does eveything the original one does and is backwardly compatible then there probably won't be much motivation to continue developing it.
Niall ----- Original Message ----- From: "Dakota Jack" <[EMAIL PROTECTED]> Sent: Wednesday, March 16, 2005 5:52 AM > I do hope that if Struts v1.3 begins to tie more than the composable > request processor to this Command/Chain business that a fork is > allowed in Struts v1.2. Once the problems with the Command/Chain idea > begin to cause "hacks" that then enslave the framework to the > Command/Chain pattern, things will become frozen rather than fluid, in > my opinion. > > > Jack --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
