Oops, meant to send this to the list. > --- On Wed, 7/16/08, Brad A Cupit wrote: > So, before annotation-based configuration, you'd setup > action chaining to have it go from the input() method > to the execute() method?
No, you'd go to form display via input(), and submit to execute(). Conceptually, like this: <action name="foo_input" method="input"> <result>/WEB-INF/jsps/foo.jsp</result> </action> <action name="foo"> <result name="input">/WEB-INF/jsps/foo.jsp</result> <result>/WEB-INF/jsps/foo_success.jsp</result> </action> I guess you *could* do it like you're suggesting, but I never did. Of course, I'm usually wrong :) There are a few different ways to implement a pattern like this--I don't know which ideas came first; someone with more WW experience could probably provide better history. > Has that style now been replaced with Validateable's > validate() method and the DefaultWorkflowInterceptor? Um, not sure; I guess I never really thought of the two as related before. In my short time with WW/S2 the input() method always skipped validation, so it always seemed to me that they worked together to implement the pattern shown above--but I could have completely misunderstood, too. > Even then, I guess I still don't understand why it is a > method on ActionSupport, if it was just a convention. So we didn't have to write our own if it didn't do anything particularly special. For example, if we were doing action initialization via Prepareable the default impl would be enough (for the above, possibly wrong, pattern). Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
