-
1. Re: JBoss EAP 6.2 still uses jboss.xml / what about EAP 6.3 onwards
jaysensharma Dec 3, 2015 11:08 AM (in response to mac2009)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.xml
The
jboss-ejb3.xml
deployment descriptor replaces thejboss.xml
deployment descriptor to override and add to the features provided by the Java Enterprise Edition (EE) definedejb3-jar.xml
deployment descriptor. The new file is incompatible withjboss.xml
, and thejboss.xml
is now ignored in deployments.EAP6 Migration guide: https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html-single/Migration_Guide/index.html
-
2. Re: JBoss EAP 6.2 still uses jboss.xml / what about EAP 6.3 onwards
mac2009 Dec 3, 2015 12:08 PM (in response to jaysensharma)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
1.
<session>
<ejb-name>OB</ejb-name>
<jndi-name>OB</jndi-name>
<local-jndi-name>OBLocal</local-jndi-name>
<method-attributes>
</method-attributes>
</session>
2.
<session>
<ejb-name>OB</ejb-name>
<jndi-name>ejb:name/name-ejb/OB!com.packagename.OBHome</jndi-name>
<local-jndi-name>java:app/name-ejb/OB!com.packagename.OBLocalHome</local-jndi-name>
<method-attributes>
</method-attributes>
</session>
And of course in the first case I get a NameNotFoundException.
So, is jboss.xml in use or not??? Or whats going here...