+++ This bug was initially created as a clone of Bug #1148961 +++ JBossStandaloneEJBContainerProvider does not respect javax.ejb.embeddable.provider property as required by EJB 3.1 specification: 22.3.3 ... The EJBContainer bootstrap class will locate all of the container providers by their provider config- uration files and call EJBContainerProvider.createEJBContainer(Map<?, ?>) on them in turn until an appropriate backing provider returns an EJBContainer. A provider may deem itself as appropriate for the embeddable application if any of the following are true : • The javax.ejb.embeddable.provider property was included in the Map passed to createEJBContainer and the value of the property is the provider’s implementation class. • No javax.ejb.embeddable.provider property was specified. If a provider does not qualify as the provider for the embeddable application, it must return null when createEJBContainer is invoked on it. ... JBossStandaloneEJBContainerProvider implementation always try to instantiate a container regardles of No javax.ejb.embeddable.provider property setting. This violates EJB specs and makes TCK6 test com/sun/ts/tests/ejb30/lite/packaging/embed/provider/Client.java to pass by pure luck or to fail on JDK8. --- Additional comment from Dominik Pospisil on 2014-10-02 14:57:23 EDT --- PR sent: https://github.com/jbossas/jboss-eap/pull/1762 --- Additional comment from Jan Martiska on 2014-10-14 02:54:32 EDT --- Verified in EAP 6.4.0.DR4. TCK regression caused by this is tracked under https://bugzilla.redhat.com/show_bug.cgi?id=1150968
PR sent: https://github.com/jbossas/jboss-eap/pull/1898
Verified in EAP 6.3.3.CR1.