> * (Optional) alternative dynamic execution mapping to execute a Commons
> Chain command
>   (essentially equivalent to the current functionality, and/or a tie-in to
> Struts Action Framework 1.3.x
>   type processing logic).

David has some good points about Chain being a bit of overkill.  I
didn't have much problem with it but then again I'm pretty familiar
with Shale and Chain.  And when you think about it, he's right.  A lot
of situations don't really call for a complex chain.

Having the *option* to call a chain sounds interesting.  Can you give
an example of the URL and the naming conventions here?

[snip]

> * For a context relative URL of the form "/execute/foo/bar", execute the
> bar() method on the managed
>   bean named "foo".  This method will take total responsibility for
> producing the output, so it can do
>   whatever it needs.

I like it.  This would be very handy indeed.

> Craig

Sean

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to