Re: Null value from a dropdown
Martin Gilday <[email protected]>
| Newsgroups | gmane.comp.java.open-symphony.webwork |
|---|---|
| Message-ID | <11676783.1165156194588.JavaMail.os-j2ee@opensymphony01.managed.contegix.com> |
> > Say you want to remove a parameter if it matches a > value, but only on a few methods and > > not all for that action. Putting both interceptors > on the stack together would not make this > > possible. > > I might miss the point, but would the following does > it. > [code] > <action name="myAction" class="foo.bar.MyAction" > method="methodOne"> > <interceptor-ref name="paramRemover"> > <param name="removeNames">paramOne</param> > <param name="removeKey">someParamValue</param> > </interceptor-ref> > .... > action> > <action name="myAnotherAction" > class="foo.bar.MyAction" method="methodTwo"> > <interceptor-ref name="paramRemover"> > <param name="removeNames">paramOne</param> > <param name="removeKey">...</param> > </interceptor> > .... > action> > [/code] > > I guess in this case we have 2 different methods > (methodOne, methodTwo) on the same action > MyAction.java and each having the same/different > parameter removed when the param value match a > certain pattern. > > rgds Yes that would work. I have always just one action defined per class, and used method= as a default to use if no !methodName was provided. --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=51757&messageID=104931#104931 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]