[
https://issues.apache.org/jira/browse/MYFACES-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848918#action_12848918
]
Jakob Korherr commented on MYFACES-2621:
----------------------------------------
I totally agree with you Leonardo here! Also I want to be able to set those
field using reflection for automated tests, so a big -1 from me on reverting
ExternalSpecifications!!!!
We can use Object getValueReference(ELContext context) here, because MyFaces is
compiled with the el-api 2.1 dependency and so it does not know the newer
method from the super class with return value ValueReference. At first I was
also not sure if this works, but I tested it and it did. Of course, it won't
compile with el-api 2.2, but the only thing to change here would be the return
type...
To your suggestion with FacesWrapper, Leonardo: we can't do this, because there
are wrappers that have to do some work before and after every method of the
wrapped ValueExpression is called (e.g. LocationValueExpression for
ValueExpressions containing #{cc}). Accessing the wrapper directly would change
the expected behavior.
> 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/[email protected]/msg55250.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
