-
1. Re: EJB not bound
bigy Oct 5, 2004 4:54 PM (in response to bigy)Here is the full error:
javax.naming.NameNotFoundException: ejb not bound
-
2. Re: EJB not bound
darranl Oct 6, 2004 3:59 AM (in response to bigy)Have you checked the console for any deployment errors?
Also have you had a look at JNDI view to see what is actually bound? -
3. Re: EJB not bound
lamontllq Mar 8, 2005 12:52 PM (in response to bigy)I've a similar problem. I tried to migrate from Websphere to JBoss 4.0.1 and I've convert my ibm-ejb-jar.xmi in jboss.xml.
I've a ejb-jar.xml like that
<enterprise-beans>
<ejb-name>DateLogique</ejb-name>
<local-home>com.DateLogiqueLocalHome</local-home>
com.DateLogiqueLocal
<ejb-class>com.DateLogiqueBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<resource-ref id="ResourceRef_1080661309044">
<res-ref-name>jdbc/popo_ddi</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
...
</ejb-jar>
and a jboss.xml like that
<enterprise-beans>
<display-name>DateLogique</display-name>
<ejb-name>DateLogique</ejb-name>
<jndi-name>ejb/com/iris/infrastructure/services/datelogique/ejb/DateLogiqueLocalHome</jndi-name>
<resource-ref>
<res-ref-name>jdbc/iris_ddi</res-ref-name>
<resource-name>jdbc/iris_ddi</resource-name>
</resource-ref>
...
this two file is in the META-INF directory
the problem is want I start my server I've this error:
org.jboss.deployment.DeploymentException: Error in jboss.xml for Bean DateLogique: found in jboss.xml but not in ejb-jar.xml
the EJB is in ejb-jar.xml and in jboss.xml with the same name.
Somebody have a idea? -
4. Re: EJB not bound
jleguen Mar 9, 2005 4:08 PM (in response to bigy)I am getting a similar problem, but in a migration from 3.2.6 - 3.2.7. I have an application that had local and remote interfaces for Stateless session beans. They are configured in ejb-jar.xml with then name "ejb/EJBProcessUser". With earlier versions 3.2.3-3.2.6 The java application looks up using the name "local/ejb/EJBProcessUser" from the env context. It works if I deploy to 3.2.6 but the same ear fails EJB not bound. A look at the JNDI names using the jmx-console shows that the bean is bound.
John Le Guen -
5. Re: EJB not bound
starksm64 Mar 9, 2005 4:24 PM (in response to bigy)See:
[JBAS-275] - 2 identical named mdbs cannot deploy
http://jira.jboss.com/jira/browse/JBAS-275