I am wondering what the best approach is for my Action classes.
I have a need for event dispatching, because some of my forms offer multiple
submit choices (buttons / images / links).
EventDispatchAction and EventActionDispatcher look good and I am planning on taking the EventDispatchAction and cobbling together some further functionality derived from various projects I've worked on over the last couple of years
- dependency injection by Spring for my services / delegates (/ daos)
- replacing all the struts parameters to my methods with a context object
- an exception handling switch
- a mechanism for handling 'on-the-fly' URL & query strings for actionForwards
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.
Regards
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
