We are using my new workflow (which I am getting ready
to put out for everyone) and have come up with a way
around this.
Because in Sequence and in Workflow, you are always in
a "Model executing a Model" situation, you can take
advantage of it. You first must get the previous
request and add the paramaters to it. Then when the
Sequence/Workflow executes the next model, it can pass
the parameter from one to the next.
This will allow a parameter to live until there is a
"return" model.
On the workflow note, don't use what is in CVS. There
is a totally new system that is going to be released.
I am going to try to get the docs done tonight and
tomorrow for a "pre-release".
-Jeff
--- Shash Chatterjee <[EMAIL PROTECTED]> wrote:
> Mike,
>
> > This is I think the favorite idea, but it doesn't
> appear to work in a
> sequence right now. E.g. if you're in model A in a
> sequence of A, B, C, and do
> something like req.setParameter("name", "value"),
> then try to do a
> getParameter("name") in B, "value" won't be there. I
> think we should call that
> a bug and fix it - alternately, don't allow a
> setParameter from within a
> model, but I prefer the former.
> >
>
> +1 for adding it to the request parameters.
>
> Shash
>
> http://keelframework.org/documentation
> Keelgroup mailing list
> [EMAIL PROTECTED]
>
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/
http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
