jboss.xml is not going to be used by JBoss any more from JBoss EAP 6.x onwards we will need to use "jboss-ejb3.xml" for the EJB3 specific container specific settings.
The jboss.xml file is going to be ignored in any case, irrespective of any condition whether we use jboss-ejb3.xml or not.
The same information is applicable for all the EAP 6.x release:
jboss-ejb3.xmldeployment descriptor replaces the
jboss.xmldeployment descriptor to override and add to the features provided by the Java Enterprise Edition (EE) defined
ejb3-jar.xmldeployment descriptor. The new file is incompatible with
jboss.xml, and the
jboss.xmlis now ignored in deployments.
Well, either something else is wrong here or jboss.xml is still used!!! I have read all the migration guides before...
I tested it again and again.
1. there is no diff in ejb-jar.xml
2. JNDI names on server start are the same
3. the only diff is in jboss.xml
And the difference in jboss.xml is
And of course in the first case I get a NameNotFoundException.
So, is jboss.xml in use or not??? Or whats going here...