RE: [OS-webwork] How to redirect to a page with parameters?

[Matthew Payne]

Two parameters works for me. e.g. <action name="unschedule" class="org.quartz.ui.web.action.schedule.UnSchedule">             <result name="success" type="redirect">../viewJobDetail.do?name=${jobName}&amp;groupName=${jobGroup}</result>        <result name="error"  type="velocity">/WEB-INF/vm/editDefinition.vm</result> </action> On Sat, 2004-01-17 at 04:39, Drew McAuliffe wrote: I haven't tried it but I'm pretty sure it would work. The "parse=true" think is pretty key, but then it uses the ${} syntax, so there's no reason I can think of that it wouldn't work for more than one param. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Woon Sent: Friday, January 16, 2004 12:53 PM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] How to redirect to a page with parameters? Drew McAuliffe wrote: I do this sort of thing a lot. I'm not sure if the approach you're taking in your xwork file is the right way but it could be. I do know that I've had success with the following:       <action name="foo" class="test.FooAction">       <!-- results -->       <result name="input" type="redirect">         <param name="location">/test.jsp?objId=${objId}</param>         <param name="parse">true</param>       </result>       <interceptor-ref name="workflowStack"/>     </action> I'm using the "parse" property to make sure that the ${} value is parsed out. Also, I'm using the "redirect" result type (dispatcher is just the normal jsp dispatcher, and it sounds like you wanted the redirect). As I said, I'm not sure if specifying the parameter separately for "objId" as part of the result will work, because I'm not sure if it will get parsed. I'm pretty sure that the static params interceptor is what allows you to separately specify the parameter as you've done, so maybe that has some parsing ability. Drew, have you been succesful in passing multiple parameters in this manner? Thanks, -Mark -- Matthew Payne <[EMAIL PROTECTED]>