jboss.xml descriptor in JBoss 7.1.1?

[bpflugfelder]

Hi @all,

I am quite new to JBoss and have to solve a tough migration task from JBoss 3.2.1 to JBoss 7.1.1. The application I have to migrate is a EAR based on EJB 2.0 and an old Struts version. Since I cannot adapt the source code of the EAR application I have to make the EJB 2.0 somehow running in JBoss 7.1.1.

One ejb jar troubles me a lot since it contains jboss.xml, jbosscmp-jdbc.xml and ejb-jar.xml descriptors. From some posts here in the user forum I came to know that jboss.xml is not supported since JBoss Version 7 any more. So, I will have to migrate the jboss.xml to jboss-ejb3.xml somehow if I am right.

However, I am not quite sure how I do this and appreciate any help on this issue. I attached the old jboss.xml descriptor as well as ejb-jar.xml. I also attached my try of a new jboss-ejb3.xml.

Best regards,

Bernhard

[nickarls]

There is a chapter on migration in https://docs.jboss.org/author/display/AS71/How+do+I+migrate+my+application+from+AS5+or+AS6+to+AS7

Otherwise, I think you'll just have to read through EJB tutorials to see which stuff can be done in plain ejb-jar.xml or jboss-ejb3.xml. Then just deploy the app and reports errors as they appear. It might even be a good idea to use a nightly build of 7.2.0-Alpha-SNAPSHOT for the migration as I've understood that missing resources etc messages have improved from 7.1.1

[bpflugfelder]

@Nicklas Karlsson: Thx for the hint of using 7.2.0-Alpha-SNAPSHOT! The missing resource messages have indeed improved.

The deployment of the EAR rodun.ear (that is the very EAR I try to migrate to Version 7.x) stops with following log messages (the complete server.log is attached).

11:09:15,543 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 29) JBAS018559: Deployed "rodun.ear"
11:09:15,562 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.naming.context.java.app.rodun.cms-ejb2.EBCategoryMetaDataMapReference (missing) dependents: [service jboss.naming.context.java.comp.rodun.cms-ejb2.SBResource.env.local-ejb.EBCategoryMetaDataMapReference]
      service jboss.naming.context.java.app.rodun.cms-ejb2.EBCategoryTypeMapReference (missing) dependents: [service jboss.naming.context.java.comp.rodun.cms-ejb2.SBResource.env.local-ejb.EBCategoryTypeMapReference]
      service jboss.naming.context.java.app.rodun.cms-ejb2.EBContentMetaDataReference (missing) dependents: [service jboss.naming.context.java.comp.rodun.cms-ejb2.SBContent.env.local-ejb.EBContentMetaDataReference]
      service jboss.naming.context.java.app.rodun.cms-ejb2.EBContentMetaLayerReference (missing) dependents: [service jboss.naming.context.java.comp.rodun.cms-ejb2.SBContent.env.local-ejb.EBContentMetaLayerReference]
      service jboss.naming.context.java.app.rodun.cms-ejb2.EBContentResourceReference (missing) dependents: [service jboss.naming.context.java.comp.rodun.cms-ejb2.SBResource.env.local-ejb.EBContentResourceReference]
      service jboss.naming.context.java.app.rodun.cms-ejb2.EBContentStatusReference (missing) dependents: [service jboss.naming.context.java.comp.rodun.cms-ejb2.SBContent.env.local-ejb.EBContentStatusReference]
      service jboss.naming.context.java.app.rodun.cms-ejb2.EBContentTypeReference (missing) dependents: [service jboss.naming.context.java.comp.rodun.cms-ejb2.SBResource.env.local-ejb.EBContentTypeReference]
      service jboss.naming.context.java.app.rodun.cms-ejb2.EBLanguageReference (missing) dependents: [service jboss.naming.context.java.comp.rodun.cms-ejb2.SBScene.env.local-ejb.EBLanguageReference]
... and many more missing dependencies

Taking for example EBCategoryMetaDataMapReference, the ejb-jar.xml defines the following:

<session>

      <ejb-name>SBResource</ejb-name>

...

     <ejb-local-ref>

        <ejb-ref-name>local-ejb/EBCategoryMetaDataMapReference</ejb-ref-name>

        <ejb-ref-type>Entity</ejb-ref-type>

        <local-home>de.inovex.cms.ejb2.resource.dao.EBCategoryMetaDataMapLocalHome</local-home>

        <local>de.inovex.cms.ejb2.resource.dao.EBCategoryMetaDataMapLocal</local>

        <ejb-link>EBCategoryMetaDataMap</ejb-link>

      </ejb-local-ref>

...

</session>

In terms of EBCategoryMetaDataMapReference I translated the old config of the old jboss.xml to jboss-ejb3.xml as follows:

<session>

                <ejb-name>SBResource</ejb-name>

                <ejb-ref>

                        <ejb-ref-name>local-ejb/EBCategoryMetaDataMapReference</ejb-ref-name>

                        <jndi-name>java:app/cms-ejb2/EBCategoryMetaDataMapReference</jndi-name>

                </ejb-ref>

...

</session>

I already tested other jndi binding names, but it did not solve the problem. Honestly, I am quite a newbie to 7.x and it might be likely some stupid error with the new absolute JNDI names.

Any help or hint is really welcome :-)

Best regards, Bernhard

[vandiesel]

Hi Bernhard,

I would like to know how you resolved the migration issue with the deployment descriptors.

If you can forward me the jboss-ejb3.xml, that would be great!

Also, let me know the issues you resolved while migration.

Thank you,

Diesel