[weld-issues] [JBoss JIRA] Commented: (WELD-234) Ambiguous dependencies error when obtaining/injecting a reference to an Extension
[
https://jira.jboss.org/jira/browse/WELD-234?page=com.atlassian.jira.plugi...
]
Pete Muir commented on WELD-234:
--------------------------------
Actually, this isn't clear in the spec. I've asked the 299 EG to clarify this in
the spec (whether we don't create a managed bean, or whether we put some extra
qualfier for the extension bean or...)
I've added a test -
org.jboss.weld.test.unit.extensions.ExtensionTest.testExtensionInjectableAsBean() - that
shows this problem.
Attaching tests like this (which are container agnostic) helps a great deal in getting
issues fixed quickly.
Ambiguous dependencies error when obtaining/injecting a reference to
an Extension
---------------------------------------------------------------------------------
Key: WELD-234
URL: https://jira.jboss.org/jira/browse/WELD-234
Project: Weld
Issue Type: Bug
Reporter: Paul Sandoz
Priority: Blocker
Fix For: 1.0.0.CR2
Attachments: jcditest.zip
When attempting to obtain a reference to an Extension (either programatically or via
@Inject) an exception is throw similar to the following:
org.jboss.weld.DeploymentException: Injection point has ambiguous dependencies.
Injection point: field
com.sun.jersey.samples.jcdibeans.resources.JCDIBeanPerRequestResource.teb;
Qualifiers:
[@javax.enterprise.inject.Default()]; Possible dependencies:
[org.jboss.weld.bean-deployment-Built-in-
Extension-foo.TestExtensionBean,
org.jboss.weld.bean-/Users/paulsandoz/Projects/jersey/branches/jersey-
1.1.4-ea-SNAPSHOT/samples/jcdi-beans-webapp/target/jcdi-beans-webapp/-ManagedBean-
foo.TestExtensionBean]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira