Thanks Ted. >> Ideally, the Actions should not contain any real business logic and should just be used as a "stepping stone". I rarely write "custom" Actions myself, but rely on a set of standard framework Actions which instantiate a business object, pass up the inputs, and pass back the outputs. This can be handled through the Struts config, but a more comprehensive XML application could work much better. <<
Can you elaborate a little on this? What standard framework Actions in particular give you this ability? >> Craig in fact proposed such a creature last year -- see the Workflow component in the Commons. I think this would jive well with what you have outlined. << Great... thanks for the pointer! I'll take a look at it... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
