JBoss EAP 6.2 still uses jboss.xml / what about EAP 6.3 onwards

[mac2009]

Hi all,

wondering a bit that JBoss EAP 6.2 still uses jboss.xml.

As mentioned in die EAP 6.2 Migration Guide the jboss.xml will be ignored.

Or is it ignored only if a jboss-ejb3.xml is contained in deployment?

And how is behaviour in 6.3 and so on? We have to upgrade from 6.2 to 6.4 soon...

Thanks for any information.

Cheers

Carsten

[jaysensharma]

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 the jboss.xml deployment 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.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

EAP 6.1: https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.1/html-single/Migration_Guide/index.html

EAP 6.2 https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html-single/Migration_Guide/index.html

EAP 6.3 https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Migration_Guide/index.html

EAP 6.4 https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html-single/Migration_Guide/index.html

[mac2009]

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...