https://bz.apache.org/bugzilla/show_bug.cgi?id=69914
--- Comment #4 from Mark Thomas <[email protected]> --- Just to add to what Chris said. Beans and Records have different naming conventions for accessors. For Beans it is getCamelCaseName(). For Records it is camelCaseName(). You have a Record with an accessor using Bean naming conventions. It works in 10.1.x because 10.1.x doesn't understand Records and treats it as a Bean. 11.0.x understands Records so it expects the Record naming convention. Backwards compatibility works both ways. If the EL 6.0 behaviour was changed to check both Record and Bean naming styles that could break other applications. Granted, that is unlikely to happen for most applications but given the number of applications I'd expect a number would be impacted. This could be changed in EL 6.1 (Tomcat 12) but that won't help you with Tomcat 11. We could add an option to Tomcat that enabled this behaviour but we try not to do that unless there is an obvious bug, high demand or similar and we aren't see that in this case. The simplest may be to add the following to your Person Record. public String fullName() { return getFullName(); } I think that will give you the behaviour you want in 10.1.x and 11.0.x but I haven't tested it. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
