>From a design POV, there are differences between params and
staticParams interceptor:
AFAIK, the parameter interceptor is called twice because it serves
this design purpose: to allow your action to execute some logic which
is dependent of *some* of the current parameter values to set up the
model
mgainty wrote:
>
>
> Andy-
> the short answer is you don't want
> user-set parameters to override your static parameters.
>
>
Well yes - but I need the parameters for doing some prepare() work. I can
see that staticParams fires after params in the default stack. I can also
see that params i
You can configure the params interceptor to ignore some parameters,
passing regular expressions to the excludeParams attribute.
http://struts.apache.org/2.x/docs/parameters-interceptor.html
musachy
On Fri, Aug 1, 2008 at 12:53 PM, Gabriel Belingueres
<[EMAIL PROTECTED]> wrote:
> staticParams prov
Andy-
the short answer is you don't want
user-set parameters to override your static parameters.
btw for 2.1.1 you also need: "actionMappingParams"
Which means your stack should be:
...
...
...
(courtesy of dale)
http://www.nabble.com/about-paramsPrepareParamsStack-t
staticParams provide some sort of default parameter injection when you
declare an action in your struts.xml, but it should be ok to override
this value if it came as a parameter. If the interceptor order would
be the opposite, then static parameters would take precedence over
regular parameters.
A
5 matches
Mail list logo
