SOAP over JMS in JBossWS using EJB 3 endpoints

Issue

• We have a JEE 6 Web application (deployed as a WAR) containing a wsdl with both SOAP over HTTP & SOAP over JMS endpoints. Some EJB 3.1 Stateless Session Beans and JPA Entities. We are able to deploy this with POJO Endpoint's (need to provide a jbossws-cxf.xml with endpoint details as spring config).

• However, we are facing the following issues:

  • Scenario 1 :
    Unable to Inject any EJB 3.1 Stateless Session Bean's using CDI & have to do a JNDI lookup. Is this an expected behaviour ?
  • Scenario 2 :
    In this scenario a POJO JMS Endpoint invokes a Stateless Session Bean A with Transaction attribute as REQUIRED which inturn invokes another Stateless Session Bean B with Transaction attribute as SUPPORTS. We were expecting that both the session bean's participate in the same transaction However, the session bean B is complaining that there is no active transaction. What are we missing ?

• The SOAP over JMS was implemented as per the instructions in the following links :
  https://docs.jboss.org/author/display/AS71/SOAP+over+JMS
  https://developer.jboss.org/wiki/JBossWS-CXFJMSTransportTutorial

• As per the documentation it seems that JBossWS currently supports POJO endpoints ONLY for JMS transport so has there been any further developments in this space to support EJB 3 end points for JMS Transport ?