[
https://issues.apache.org/jira/browse/MYFACES-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848895#action_12848895
]
Jan-Kees van Andel commented on MYFACES-2621:
---------------------------------------------
My first implementation of ExternalSpecifications was purely designed for
performance, relying on the ClassLoader to safely publish the variables.
Testability was the reason to refactor it into synchronized methods.
If you guys don't mind about less testability, we can always revert it to the
original implementation which is probably the fastest possible implementation
(no volatile/synchronized needed).
A Double Checked Locking (DCL) implementation would also be a valid choice,
since we depend on Java 5+ and the Java 5 JMM guarantees DCL correctness. That
way, the first access requires an exclusive lock and consecutive calls only do
volatile reads. This is still pretty fast without compromising testability.
I would say, revert ExternalSpecifications to its original form and then look
at Leonardo's suggestion.
> 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.
