We are now able to access Session EJBs, but having issues accessing our (EJB 2.0) Entity EJBs. The container does not bind them to the JNDI namespace (I checked on the JMXConsole) and I am getting a NameNotFoundException. I think it treats EJB 2.0 Entities as EJB 3.0 Entities which do not need to get bound to the JNDI namespace. Here is part of the exception trace: anonymous wrote : 09:40:55,941 ERROR [ContactCompositeBean] javax.naming.NameNotFoundException: PasswordHistory not bound | com.creativesolutions.ems.EJBUtil.EJBLoaderException: javax.naming.NameNotFoundException: PasswordHistory not bound | at com.creativesolutions.ems.EJBUtil.EJBLoader.getPasswordHistoryHome(EJBLoader.java:4334) | at com.creativesolutions.ems.compositeBean.ContactCompositeBean.savePasswordHistory(ContactCompositeBean.java:1778) | at com.creativesolutions.ems.compositeBean.ContactCompositeBean.changeUserPassword(ContactCompositeBean.java:586) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175043#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...