You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Christian Wolfgang Stone (JIRA)" <ji...@apache.org> on 2013/04/01 06:45:15 UTC

[jira] [Closed] (WW-4035) OGNL no longer parsing dynamic parameters in results

     [ https://issues.apache.org/jira/browse/WW-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Wolfgang Stone closed WW-4035.
----------------------------------------

    Resolution: Not A Problem

I believe that this was treated as a freemarker file and not OGNL.  While this is completely necessary for Freemarker, this should not be necessary for OGNL and is an invalid statement (if statement instead of computer format). 
                
> OGNL no longer parsing dynamic parameters in results 
> -----------------------------------------------------
>
>                 Key: WW-4035
>                 URL: https://issues.apache.org/jira/browse/WW-4035
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Actions
>    Affects Versions: 2.3.12
>            Reporter: Christian Wolfgang Stone
>            Priority: Critical
>
> Suddenly OGNL seems to not parse dynamic parameters in the result set.
> <action name="submitCart" class="net.x.AccountOrderHandler"  method="submitOrder">
>     <interceptor-ref name="memberOrder"/>
>     <result name="success" type="redirect">/authMember/viewOrder.do?orderId=${orderId?c}</result>
> </action>
> In this case the expected successful result should be
>      /authMember/viewOrder.do?orderId=1234
> The result seems to be (suddenly)
>      /authMember/viewOrder.do?orderId=
> I am currently building in debug mode to see if I can find the exact cause.  However, I wanted to report this immediately in case some of the refactoring of OGNL has led to this.  I will continue to dig for more information, but I want to alert you of this potentially major issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira