-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
1.1.22
-
None
service-ref/service-ref-name in ejb-jar.xml/jboss.xml is not creating an env binding. See SLSB, ejb-jar.xml, jboss.xml, and JNDIView for SLSB java:comp/env:
java:comp namespace of the component jboss.j2ee:jar=webservices-test.jar,name=WebServiceRefBean,service=EJB3 :
+- EJBContext (class: javax.ejb.EJBContext)
+- TransactionSynchronizationRegistry[link -> java:TransactionSynchronizationRegistry] (class: javax.naming.LinkRef)
+- UserTransaction (class: org.jboss.ejb3.tx.UserTransactionImpl)
+- env (class: org.jnp.interfaces.NamingContext)
+- org.jboss.webservicestest.WebServiceRefBean (class: org.jnp.interfaces.NamingContext) | |
+- serviceRef (class: org.jboss.ws.core.jaxws.client.ServiceReferenceable) +- ORB[link -> java:/JBossCorbaORB] (class: javax.naming.LinkRef) |
- blocks
-
EJBTHREE-1152 service-ref in ejb-jar.xml is ignored
-
- Resolved
-
- relates to
-
JBAS-8527 ClientContainer should not use server side WebServiceRefHandler
-
- Closed
-