Jeff: > 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.
Ah - so you get the req.getPreviousRequest() and setParameter on that? I'll have to give that a try. I think as long as we come up with a single recommended way of doing it we're all set. > This will allow a parameter to live until there is a > "return" model. Yes, I see what you mean... > 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". Great! Look forward to working with it - what's there already is pretty powerful, so I'm definitely looking forward to the next iteration! :-) 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
