[
https://issues.apache.org/jira/browse/MYFACES-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849238#action_12849238
]
Jakob Korherr commented on MYFACES-2621:
----------------------------------------
We need the ValueReference because it contains the base object and the property
name to which the ValueExpression resolves. This is needed in BeanValidator,
because we need to get the class of the managed bean and the right property
name to get the right annotations out of it!
Now with el-api 2.1 there is the trick to resolve the ValueExpression with a
decorated ELContext and a special ELResolver to get both base object and
property name (see class BeanValidator for the exact implementation). The new
el-api however provides a method for this case called getValueReference() and
the spec says that if it is available, we must use it instead of the trick.
I'll try some things here, reflection and/or custom wrappers and figure out
what is the best!
> 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.
