]
jaikiran pai commented on EJBTHREE-2163:
----------------------------------------
Actually, the IllegalStateException being thrown by the ClientContainer is a bug in the
application client container. It shouldn't be using a server side
WebServiceRefHandler. I'm going to rollback your last commit and track the
IllegalStateException issue here
service-ref not creating env binding
------------------------------------
Key: EJBTHREE-2163
URL:
https://jira.jboss.org/browse/EJBTHREE-2163
Project: EJB 3.0
Issue Type: Bug
Components: ejb3
Affects Versions: 1.1.22
Environment: EAP 5.0.1
Reporter: William DeCoste
Assignee: Carlo de Wolf
Attachments: ejb-jar.xml, EJBTHREE-2163.patch, jboss.xml, WebServiceRefBean.java
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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: