I haven't tried it, but the Result does take a parameters array, which, depending on how it is handled, will allow expressions to be evaluated. In addition, I thought about adding support for expressions within the location of the Result annotation. This would allow you to use non-action redirects with parameters. Something like this:

@Result(name="success", location="/purchase/complete?id=${po.id}", type="redirect")

I'll try and get an example running today that tests this dynamic parameters and also look into evaluating the result location via the OGNL stack. This will probably need to be handled inside the results themself, since Smart URLs doesn't actually do any of the work of handling the results. It just figures out which ones to use.

-bp


Ted Husted wrote:
I filed issues for the last round at Google Code, and threw in one or
two other tweaks.

Here's a bigger question:

For redirects, would we be able to support "Dynamic Parameters for
Redirects"? Mark has a good description of the conventional S2
approach here:

 * http://www.vitarara.org/cms/struts_2_cookbook/post_and_redirect

-Ted.

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


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to