[
https://issues.apache.org/jira/browse/MYFACES-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848924#action_12848924
]
Leonardo Uribe commented on MYFACES-2621:
-----------------------------------------
I miss one wrapper:
org.apache.myfaces.view.facelets.tag.jstl.core.IteratedValueExpression
In the case of LocationValueExpression, IndexedValueExpression and
IteratedValueExpression we can use two wrappers hack. I'm just exploring
ideas, to see which solution looks better.
Really I don't like to change the signature of a method. If the method does not
compile with el-api 2.2, that says something is wrong. In my personal opinion,
the fact that it works, but does not compile with el-api 2.2 makes it not
viable, because we could expect in the future (other versions of jsf) to
upgrade to el-api 2.2, and in that case our code will break.
Other thing we can do is when ValueReference returns null, do the same that we
do when el 2.2 is not available, but I ignore the implications of do this. All
depends of why and what we do with ValueReference in bean validation. Note I
don't know all details behind current bean validation implementation.
> BeanValidation does not work with Unified EL 2.2
> ------------------------------------------------
>
> Key: MYFACES-2621
> URL: https://issues.apache.org/jira/browse/MYFACES-2621
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-beta-3
> Environment: bean validation 1.0.0.GA, unified el 2.2
> Reporter: Jakob Korherr
> Assignee: Jakob Korherr
>
> When using the new Unified EL 2.2, BeanValidation does not work, because
> _BeanValidatorUELUtils.getUELValueReferenceWrapper() always returns null.
> See also the related thread on the mailing list:
> http://www.mail-archive.com/us...@myfaces.apache.org/msg55250.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
