Issue with isDefault variable in AddressImpl

[sai]

Scenaio: I am showing all the addresses for a customer , but I need to show the address that is currently a default address. When I am trying to place check for default address I am having issue

When I am trying to access the variable (isDefault) from AddressImpl.java on JSP page I am getting below exception. When I tried to search through felt like this is due to 'default' being the keyword used is throwing exception.

The bolded part of the code snippet below is causing trouble. I was wondering if you might have experienced similar issue.

Any help and work around for this much appreciated.

Thank you for the continuous support.

**********************************************************************************************************
2: <div id="addresses">
3: <table>
4: <c:forEach var="customerAddress" items="${addresses}">
5: <tr> <td>${customerAddress.address.default}</td> </tr>
6: <tr> <td>${customerAddress.addressName}</td> </tr>
7: <tr> <td>${customerAddress.address.addressLine1}</td> </tr>
8: <tr> <td>${customerAddress.address.city}</td> </tr>


Stacktrace:] with root cause
javax.el.ELException: The identifier [default] is not a valid Java identifier as required by section 1.19 of the EL specification (Identifier ::= Java language identifier). This check can be disabled by setting the system property org.apache.el.parser.SKIP_IDENTIFIER_CHECK to true.
at org.apache.el.parser.AstDotSuffix.setImage(AstDotSuffix.java:46)
at org.apache.el.parser.ELParser.DotSuffix(ELParser.java:1067)
at org.apache.el.parser.ELParser.ValueSuffix(ELParser.java:1033)
at org.apache.el.parser.ELParser.Value(ELParser.java:978)
at org.apache.el.parser.ELParser.Unary(ELParser.java:948)

[bpolster]

I'm unable to test this issue right away.

You can try replacing the out of box AddressImpl with one that includes isDefaultAddress / setDefaultAddress methods that just wrap the existing isDefault. If that works for you, you can submit a pull request with the change or just let us know and we'll include that in the next patch.

[sai]

I am running the application on Tomcat server, thought if this might be the reason why you are not able to replicate. Tomcat does syntax validation check for all the expressions in JSP resulted in this issue.

Do you suggest to disable EL expression checks in Tomcat like below.

JAVA_OPTS="$JAVA_OPTS -Dorg.apache.el.parser.SKIP_IDENTIFIER_CHECK=true"
export JAVA_OPTS

Even if I wrap around with different method signatures I am not sure how that will work, because when I access the variable in JSTL tags, I will be accessing the variable directly and it internally interprets by adding the getter's to fetch the data.

Can you please elaborate on what you meant.