https://bz.apache.org/bugzilla/show_bug.cgi?id=69914
Christopher Schultz <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Christopher Schultz <[email protected]> --- I think this is "expected behavior". In Jakarta EL 6.0 (which Tomcat 11.0 supports), record types are not considered to be Java beans. You can only use record components as properties for a record-class. So you can't have a "synthesized property" like you describe in your test. This change can be found in Appendix 1 of the EL 6.0 spec document[1], linked to issue #201 [2]. It seems to me that there could be scope for including non-record-components in the RecordELResolver but it wouldn't be portable (between containers) until it becomes a part of the official specification. You might argue in favor of it in terms of "backward compatibility" which I think might be a fairly strong argument for getting this retroactively added to the 6.0 specification as some kind of erratum. I'm no expert on EL, the Jakarta release process, etc. but there are those around here who are much more well versed in such things. I'm going to close this as INVALID because it's "not a bug in Tomcat" since we follow the spec, but as the spec changes, we will update accordingly. I would highly recommend that you file an issue with the Jakarta EL Specification [3] https://github.com/jakartaee/expression-language/issues to get this settled. [1] https://jakarta.ee/specifications/expression-language/6.0/jakarta-expression-language-spec-6.0#changes-between-6-0-and-5-0 [2] https://github.com/jakartaee/expression-language/issues/201 [3] -- 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]
