jon * wrote:
>
> >From the scheduler .wm templates...
>
> $edituri?jobid=$job.getId()
>
> So, the problem with this is that $edituri is generated from a DynamcURI()
> which is probably the correct thing to do, the problem with this is that if
> you have cookie's turned off, then there is already going to be a "?" in the
> URL because the JServSessionId will be inserted into $edituri.
>
> Now, this is one solution that I would like something extremely clean for
> since it will potentially be used in bazillions of different places. Any
> suggestions on how to hand this? What would be REALLY cool is the ability to
> set parameters from within WM, but I'm not sure if this is possible (I don't
> think it is)...something like this:
>
> $dynamic.setScreen("edit.wm").addPathInfo("jobid", $job.getId() )
This was an oversite by me in the wm screens ( i didn't think about cookies).
I really don't think we need to add anything to accomplish what you
suggest.
I could set this all up in the Turbine screen ahead of time.
For example:
Instead of doing this in the WM screen - $edituri?jobid=$job.getId()
I could build the DynamicURI in the Turbine screen - add the pathInfo as needed
and pass the complete URI to WM. -
//All in the Turbine Screen
DynamicURI uri = new DynamicURI(data,"NextScreen");
uri.addPathInfo("jobid", job.getId())
//OR addQueryData(...)
context.put("edituri", uri);
Wouldn't this work??
--
Dave
[EMAIL PROTECTED]
your flame > /dev/null
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
