[seam-issues] [JBoss JIRA] Commented: (SEAMVALIDATE-18) ValidationExtension conflicts with Weld built-in Validator

Chris Burnley (JIRA) jira-events at lists.jboss.org
Mon Jul 11 16:32:24 EDT 2011

    [ https://issues.jboss.org/browse/SEAMVALIDATE-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613572#comment-12613572 ] 

Chris Burnley commented on SEAMVALIDATE-18:

This is happening with ValidatorFactory too under JBoss 6.0.0.Final and Seam Validation 3.0.0.Final

> 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 at 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


More information about the seam-issues mailing list