Thank you very much for this hint,
it is exactly what I meanwhile have implemented as fallback.
Only disadvantage in comparison to an ognl expression is that in case of
change I have
to change action (code) and recompile ...
What do you mean with overly-complex in detail?
the approach trying to catch as much actions with one action configuration?
(*_*_*)
I read about this as "best practice" in some struts documentation ...
Would you recommend from your experience other style?
Thanks again,
basti
newton.dave wrote:
>
> --- lbastil <[EMAIL PROTECTED]> wrote:
>> can I use in struts.xml complex ognl statements?
>
> Well... yes, but there's no reason to in this usecase.
>
>> <action name="*_*_*" method="{3}" class="{2}Action">
>> <result name="back" type="redirect-action">
>> {1}_<target>_show.action
>> </result>
>
> Expose a "target" property in your action and do the
> lookup there; the destination of your redirect-action
> would then be:
>
> {1}_${target}_show.action
>
> Or if it's a 1-to-1 mapping change the naming scheme.
>
> Still and all, it seems overly-complex.
>
> d.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/-s2--forward-to-another-action--tf4712685.html#a13488289
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
