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

["Christian Wolfgang Stone (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WW-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618600#comment-13618600 ] 

Christian Wolfgang Stone commented on WW-4035:
----------------------------------------------

I am digging into the stack.  I see that Ognl.java:112 throws a ParseException with the expression "orderId?c"
 
"ognl.ParseException: Encountered "<EOF>" at line 1, column 9.
Was expecting one of:
    "?" ...
    ":" ...
    "||" ...
    "or" ...
    "&&" ...
    "and" ...
    "|" ...
    "bor" ...
    "^" ...
    "xor" ...
    "&" ...
    "band" ...
    "==" ...
    "eq" ...
    "!=" ...
    "neq" ...
    "<" ...
    "lt" ...
    ">" ...
    "gt" ...
    "<=" ...
    "lte" ...
    ">=" ...
    "gte" ...
    "in" ...
    "not" ...
    "<<" ...
    "shl" ...
    ">>" ...
    "shr" ...
    ">>>" ...
    "ushr" ...
    "+" ...
    "-" ...
    "*" ...
    "/" ...
    "%" ...
    "instanceof" ...
    "." ...
    "(" ...
    "[" ...
    <DYNAMIC_SUBSCRIPT> ...
    "(" ...
    

Is it possible the "?c" is causing the error now? I hope not, as removing localized display is necessary for large integers "1,234" will not work and "1234" will.

                
> 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