Ok I see it now. The staticparams interceptor adds the params to the
request params map, so that would explain why it is called again. We
could add a setting to the result to prevent this if needed.

musachy

On Fri, Jul 17, 2009 at 10:18 AM, Ritvars Rundzāns<rrundz...@gmail.com> wrote:
>        <action name="person-*-*" class="example.Person">
>            <param name="cmd">{1}</param>
>            <param name="id">{2}</param>
>
>            <result>jsp/abc.jsp</result>
>        </action>
>
>>> You *do
>>> not* need to add "param" to your action mapping to get the parameters
>>> bound the class fields.
>
> I understand that. As you can see, example request (/person-aaa-bbb?dum=ccc)
> gives 1 request param (classical meaning, bound automaticaly) , and extracts
> 2 params from URI part before *?* (THIS, I GUESS, *CANT BE BINDED*
> AUTOMATICALY).
>
> I DO NOT pass cmd and id as request params (classical meaning: ?param=val)
> in this example. But they are passed, thats true.
>
> Ok, write me then action mapping , that urls like /person-aaa-bbb?dum=ccc
> maps to action PersonAction, and sets 3 params - cmd, id and dum.
>



-- 
"Hey you! Would you help me to carry the stone?" Pink Floyd

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

Reply via email to