On 7/23/06, Adam Hardy <[EMAIL PROTECTED]> wrote:
- dependency injection by Spring for my services / delegates (/ daos)
S2 uses Spring as its default object factory, and Action properties can be injected from Spring by matching the property name with the object factory ID.
- replacing all the struts parameters to my methods with a context object
S2 uses a content object internally, so that seems in line.
- an exception handling switch
Like S1, S2 includes a declarative exception handler.
- a mechanism for handling 'on-the-fly' URL & query strings for actionForwards
Like S1, S2 lets you specify a "default" action to use when nothing else matches. Wildcards are also supported.
I expect this won't take me too long to achieve (a day or two) but I would still like to >'future-proof' what I write - or should I say, 'future-orientate', since experience tells me that most 'future-proofing' underestimates the wild changes that the
future may bring.
Can anyone involved in struts 2 tell me about potential brick walls that this sort of Action base class and its children would be heading into? I checked out the
dev list for hints and
saw oblique references to Chain of Commands but couldn't guage much
from the threads
there.
S2 doesn't use Commons Chain internally. S2 relies on the notion of "interceptors" to do what we did in S1 with the Chain of Commands. Essentially, interceptors are POJO filters that let us run custom code before and after a key event, like invoking an Action class. The package that delivers the interceptor mechanism is XWork. XWork also handles matcing things like URIs to action mappings and it provides the base validation framework. Surprisingly little is actually in Struts 2 itself. Most of the functionality derives from XWork, which is web-neutral. XWork is already being used to power other frameworks. If I had understood interceptors and XWork better when we were creating Commons Chain, I would have pushed harder for us to use XWork in 1.3 instead of Commons Chain. Jason tried to explain it to me once, but it didn't click. I in turn mentioned using XWork with Struts to Don Brown, which became the nexus of TI, which evolved into the merger.
Regards Adam
-- HTH, Ted. * http://www.husted.com/struts/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
