[
https://issues.jboss.org/browse/JBIDE-14034?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-14034:
----------------------------------------
So the EJB project is not in the WAR classpath. This is the problem. JBoss Tools looks at
Eclipse project's class path and can't see EJB beans in the WAR since they are
unavailable for Eclipse Java Tooling.
You can try to create any Java class in the war project and use any class from EJB project
there. It won't compile in Eclipse because the EJB project is not in War classpath.
It will work on your server after deploying since both the EJB JAR will be available in
the WAR classpath there.
It's how Eclipse works and we can do nothing here.
So you have to add your EJB project to the WAR project's class path for the tools.
CDI EAR - EL suggestion box does not contain EJB beans
------------------------------------------------------
Key: JBIDE-14034
URL:
https://issues.jboss.org/browse/JBIDE-14034
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Reporter: Marián Labuda
Assignee: Alexey Kazakov
Fix For: 4.1.x
While testing CDI EAR in JBDS i found out, that EJB beans from EJB module are not visible
through EL in WAR module.
EARProject
\--WARProject (view e.g. home.xhtml)
\--EJBProject (EJB session bean e.g. stateful bean)
--
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