on 8/1/01 10:16 PM, "Mike Haberman" <[EMAIL PROTECTED]> wrote:
>
> Is anyone interested in an action stack/queue? I have it working in 3.0.
> on the template side you do:
>
> $link.pushAction("a1").pushAction("a2").addQueryInfo(....
>
> then in the pipline
>
> list = data.getActionQueue()
> for each item in list, execute it
>
>
> We could deprecate setAction() in favor of pushAction or enqueueAction.
> I know jason is still working on the pipeline stuff and has asked to hold
> off on commits, so I haven't committed it yet. But I can if anyone else
> might find it useful, let me know.
>
> mike
JUST MY OPINION
I still think that this is a bad design idea since what you will end up with
is only executing multiple doPerform() methods. You are also not promised
any order of execution since the browser may encode the variables in any
order and the servlet container/httpd may decode them in any order.
I'm also not really sure how that is any better than encoding the business
logic into the BO's and then referencing them in the Actions appropriate
methods mapped with ActionEvents.
In fact, I claim that it is more confusing and that the encoding of this
business logic (ie: what to execute and in what order) does not belong in
the templates.
I don't say this very often, but I'm also -1 on including this in Turbine
proper. I don't feel that it belongs and encourages bad design of
applications. I'm also -1 on deprecating setAction().
$0.00
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
