[jbosstools-issues] [JBoss JIRA] (JBIDE-9772) Unavailable beans for dependent projects
Viacheslav Kabanovich (Commented) (JIRA)
jira-events at lists.jboss.org
Fri Oct 28 17:47:45 EDT 2011
[ https://issues.jboss.org/browse/JBIDE-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638400#comment-12638400 ]
Viacheslav Kabanovich commented on JBIDE-9772:
----------------------------------------------
The case is more complex. Jar gets to A through project C which is added as a Maven dependency. We detect parent projects reading class path entries, but we do not get project C in that way.
> Unavailable beans for dependent projects
> ----------------------------------------
>
> Key: JBIDE-9772
> URL: https://issues.jboss.org/browse/JBIDE-9772
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: CDI
> Affects Versions: 3.3.0.M3
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 3.3.0.Beta1
>
>
> EXECUTE: Download/clone and install http://seamframework.org/Seam3/SecurityModule as an existing maven project. Make sure CDI support is enabled for the projects.
> EXECUTE: Open /seam-security-external/src/main/java/org/jboss/seam/security/external/openid/OpenIdAuthenticator.java
> FAILURE: There is a warning "No bean eligible for the injection point" at
> {code}
> @Inject
> HttpServletResponse response;
> {code}
> It seems that if we have project A and project B (B depends on A) and project A has a jar which is not in project classpath of project B then beans from this jar is not available for injections of project A.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list