[jbosstools-issues] [JBoss JIRA] (JBIDE-14034) CDI EAR - EL suggestion box does not contain EJB beans

[ https://issues.jboss.org/browse/JBIDE-14034?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-14034 at 4/17/13 1:51 AM: ---------------------------------------------------------------- ad 1: I use JBDS Version: 6.0.1.GA Build id: GA-v20130327-2052-B361 ad 2: Projects are created through wizards (CDI -> CDI Web project & EJB -> EJB project). There isn't support for maven by default and I didn't add it into the projects. ad 3: I hadn't added CDI support for EJB project before I created this issue. I tried it add a moment ago, but it didn't worked. Still beans are not visible (in suggestionBox there are no proposals), but after deployment of the project it works. I have also tested managed beans (injected EJB beans from EJB module into CDI beans in WAR module and adding EJB module to the classpath of the WAR module) and there it works - EJB module has to have added CDI support and to be on the classpath of the WAR project. But I don't know, if it's desirable to add EJB on that classpath in every case, however it is not required (as I wrote, project had deployed and had worked without adding EJB to the classpath of the WAR, but problem with EL still persisted). was (Author: mlabuda): ad 1: I use JBDS Version: 6.0.1.GA Build id: GA-v20130327-2052-B361 ad 2: Projects are created through wizards (CDI -> CDI Web project & EJB -> EJB project. There isn't support for maven by default and i didn't add it into the projects. ad 3: I hadn't added CDI support for EJB project before I created this issue. I tried it add a moment ago, but it didn't worked. Still beans are not visible (in suggestionBox there are no proposals), but after deployment of the project it works. I have also tested managed beans (injected EJB beans from EJB module into CDI beans in WAR module and adding EJB module to the classpath of the WAR module) and there it works - EJB module has to have added CDI support and to be on the classpath of the WAR project. But I don't know, if it's desirable to add EJB on that classpath in every case, however it is not required (as I wrote, project had deployed and had worked without adding EJB to the classpath of the WAR, but problem with EL still persisted). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira