Skip to content

Commit

Permalink
Fix #159. Clarify process for mapping expressions with params to methods
Browse files Browse the repository at this point in the history
  • Loading branch information
markt-asf committed Jul 7, 2021
1 parent 7d506fd commit ab8e8c0
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion spec/src/main/asciidoc/ELSpec.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
:sectnums!:
== Jakarta Expression Language, Version 4.0

Copyright (c) 2013, 2020 Oracle and/or its affiliates and others.
Copyright (c) 2013, 2021 Oracle and/or its affiliates and others.
All rights reserved.

Eclipse is a registered trademark of the Eclipse Foundation. Jakarta
Expand Down Expand Up @@ -330,6 +330,11 @@ signature, and there is therefore no coercion performed. If the expected
signature is not provided at parse time, then at evaluation, the method
is identified with the information of the parameters in the expression,
and the parameters are coerced to the respective formal types.
The method must be identified using the same process as that described in
section 15.12.2 of the Java Language Specification, version 11 with the
addition that coercion resolution is considered to be less specific than
overload resolution.


==== Literal-expression

Expand Down Expand Up @@ -2932,6 +2937,10 @@ This appendix is non-normative.
* https://github.com/eclipse-ee4j/el-ri/issues/157[#157]
Generics are now used where appropriate throughout the API

* https://github.com/eclipse-ee4j/el-ri/issues/159[#159]
Clarify expected behaviour when matching expressions to methods based on
parameter types

=== Changes between 4.0 and JSR 341

* The API has moved from the `javax.el` package to the `jakarta.el`
Expand Down

0 comments on commit ab8e8c0

Please sign in to comment.