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 is set to fire twice in the paramsPrepareParams stack and
that it fires after params. What I don't understand is why staticParams
doesn't fire twice in the struts-supplied pPP stack. Unless there is a
sensible design decision why it should not, I'm going to propose an RFE that
it should

Seems to me that the current set-up allows user-set params to overide my
static parameters if they are required in a prepare() which is just plain
wrong.


mgainty wrote:
> 
> btw for 2.1.1 you also need: "actionMappingParams"
> 
> 
> Which means your stack should be:
> 
> <interceptor-stack name="paramsPrepareParamsStack">
> 
> .......
> <interceptor-ref name="params"/>
> 
> <interceptor-ref name="actionMappingParams"/>
> 
> <interceptor-ref name="staticParams"/>
> 
> ...
> 
> <interceptor-ref name="prepare"/>
> 
> ...
> 
> <interceptor-ref name="params"/>
> 
> <interceptor-ref name="actionMappingParams"/>
> 
> <interceptor-ref name="staticParams"/>
> 
> 
> </interceptor-stack>
> 
> (courtesy of dale)
> http://www.nabble.com/about-paramsPrepareParamsStack-td15462644.html
> 
> Martin 
> 

Thanks. This is useful info and I missed the other thread when I searched
earlier. I'm disappointed to see that I will have to refactor stuff
(struts.xml) when I shift to 2.1.x when if they were included correctly
(IMHO) in the pPP stack that gets distributed, I wouldn't need to do that.


What's the procedure for requesting enhancements?

Later,

Andy

-- 
View this message in context: 
http://www.nabble.com/paramsPrepareParams-vs.-staticParams-tp18773842p18801209.html
Sent from the Struts - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to