Steve:
> > Does anyone have a strong view as to how this should happen? I know
> > SequenceContext exists, but it's specific to sequences, and not generic enough to
> > also be used in Workflows (isn't it?) My vote would be for "per request" context
> > to be the request parameters (and attributes), and for these to "survive" into the
> > next model unless they are specifically overridden by the sequence (or workflow)
> > by configuration.
>
> How about setting the value in the Request or Response object?
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.
Mike
>
> Regards,
> Steve
>
> --
> Java/J2EE Developer/Integrator
> Co-Chair, Dallas/FortWorth J2EE Sig
> 214-724-7741
>
>
> http://keelframework.org/documentation
> Keelgroup mailing list
> [EMAIL PROTECTED]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
Michael Nash
JGlobal Ltd
Next-Generation Web Application Development and Open Source Support
http://www.jglobal.com
Bahamas Commerce and Trade
Offshore eCommerce Hosting and Business Services
http://www.bahamascommerce.com
http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
