[
https://issues.apache.org/jira/browse/MYFACES-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848829#action_12848829
]
Jakob Korherr commented on MYFACES-2621:
----------------------------------------
The problem here is that the ValueExpression on which we invoke
getValueReference() via reflection is a TagValueExpression and not directly a
ValueExpression implementation of the unified el 2.2. So getValueReference()
always returns null here, because it is not implemented.
We now have two opportunities:
1) Just don't care if el-2.2 is available and get the right base and property
the old fashioned way
2) Try to extract the real ValueExpression out of a series of wrappers and
invoke getValueReference() on it
I tend to 1) here, because a) it will always work correctly and b) we won't be
much slower as with 2) here, because we need to use reflection here a couple of
times in order to make it work and I don't think that this is very fast.
Anyway, I will do some performance tests and find out what is faster.
Does anyone know if there is a scenario where our "old-fashioned" way to
retrieve the base and the property of the ValueExpression will break with the
new unified el?
> 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.
