"First, push as much business and data access logic as possible out of
the Action class and into a POJO facade that the Action can call. In
this way, you can test all that outside of the Action."
My question lies in how do you scale this for 10 actions? 20? 50? Do
you have 1 facade for all actions (ActionSupport.java) or do you break
it down more granular (LogonActionSupport, LookupActionSupport, etc)?
If so, do you recommend then that I keep 1 main support class that each
of these secondary support classes extends?
LoginAction extenbs LogonActionSupport
LogonActionSupport extends ActionSupport (or do we skip this second
layer, and have it extend Preparable?)
ActionSupport extends Preparable, etc
Testing and jUnit test cases look like they may take as long as the dev
itself, but it's gotta be done.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
