Re: OGNL upgrade in 2.3.28 breaks expressions

Hi, It's due to fixed OGNL version which properly supports JavaBean Specifications now. You can revert to prior version of OGNL to keep the old behaviour (security fixes weren't related to OGNL) See those issues https://issues.apache.org/jira/browse/WW-3909 https://issues.apache.org/jira/browse/W

OGNL upgrade in 2.3.28 breaks expressions

It appears that a change in OGNL 3.0.13 with 2.3.28 breaks expressions that reference properties beginning with at least two capital letters. Previously, a getter like "getXXX()" could be referenced with OGNL "xXX", but these must be changed to "XXX". Is this expected behavior? It's a breaking cha