[seam-issues] [JBoss JIRA] Commented: (SEAMVALIDATE-18) ValidationExtension conflicts with Weld built-in Validator
[
https://issues.jboss.org/browse/SEAMVALIDATE-18?page=com.atlassian.jira.p...
]
Gunnar Morling commented on SEAMVALIDATE-18:
--------------------------------------------
Thanks for the report, I'll look into this.
Does the problem only occur when running with the full Seam 3 stack or also when only
using Seam Validation? The hello-world-example which is part of Seam Validation deploys
and runs successfully on GlassFish v3 and JBoss AS 6, so I'm somewhat irritated by
this exception. I'd also expect Weld's validation service to be registered before
any extensions are executed.
Could you maybe provide a sample project demonstrating the problem?
ValidationExtension conflicts with Weld built-in Validator
----------------------------------------------------------
Key: SEAMVALIDATE-18
URL: https://issues.jboss.org/browse/SEAMVALIDATE-18
Project: Seam Validation
Issue Type: Bug
Reporter: Jan Groth
Assignee: Gunnar Morling
Beeing on a project with the full Seam 3 stack, using:
{code}
@Inject
private Validator validator;
{code}
results in a deployment exception:
{{WELD-001318 Cannot resolve an ambiguous dependency between}}
org.jboss.seam.validation.ValidationExtension$2@38f8cf74,
Built-in Bean [javax.validator.Validator] with qualifiers [@Default]
I suspect the following code from ValidationExtension.java to be unaware of the Weld
built-in component "javax.validator.Validator":
{code}
// do nothing, if Validator already exists
if (!bm.getBeans(Validator.class).isEmpty()) {
return;
}
{code}
If the code is executed it works fine, but it seems as if the Weld-Component is installed
_after_ ValidationExtension registers its validator...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira