[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7950) Abstract classes is being considered injectable
[
https://issues.jboss.org/browse/JBIDE-7950?page=com.atlassian.jira.plugin...
]
Nicklas Karlsson commented on JBIDE-7950:
-----------------------------------------
Which are the ambiguous resolves according to the log?
My guess:
We have the injection type Project.
AbstractProject is abstract so it shouldn't be a candidate for injection
ProjectImpl is an actual Project so we have one candidate
The producer method CurrentProject.getCurrent is another candidate for Project so there we
have our second
I think you'll have to strangle ProjectImpl with @Typed({}) so your producer method is
free to produce the one we need.
Abstract classes is being considered injectable
-----------------------------------------------
Key: JBIDE-7950
URL: https://issues.jboss.org/browse/JBIDE-7950
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.2.0.Beta2
Reporter: Max Andersen
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 3.2.0.CR1
public interface Project {
}
public abstract class AbstractProject implements Project {
}
public class ProjectImpl extends AbstractProject {
}
@Singleton
public class CurrentProject {
@Produces
@Default
@Dependent
public Project getCurrent()
}
and then:
@Inject Project project;
And I get "Multiple beans are eligible for injection to the injection point"
Open All elgible beans seem to consider getCurrent() *and* the abstract class - but for
some reason not ProjectImpl as elgible.
Should it not just be getCurrent() ?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira