AS7 "Failed to define class" error with jboss-deployment-structure configuration

[jsebfranck]

Hi,

I'm trying to deploy an ear containing one war and two jar :

myear.ear

|--- mywebapp.war

|--- myjar1.jar

|--- myjar2.jar

The jar myjar1.jar uses classes of the jar myjar2.jar. I have the following error during the deployment :

(MSC service thread 1-5) Failed to define class com.xxxxxxxx in Module "deployment.myear.ear.myjar1.jar:main" from Service Module Loader: java.lang.LinkageError: Failed to link com.xxxxxxxxx (Module "deployment.myear.ear.myjar1.jar:main" from Service Module Loader)

...

Caused by: java.lang.NoClassDefFoundError: com/xxxxxxxxxx

So I tried to configure the dependencies between both jar in the META-INF/jboss-deployment-structure.xml file :

<jboss-deployment-structure>

  <ear-subdeployments-isolated>false</ear-subdeployments-isolated>

  <deployment>

    <dependencies>

      <module name="deployment.myear.ear.myjar1.jar" />

      <module name="deployment.myear.ear.myjar2.jar" />

    </dependencies>

  </deployment>

  <sub-deployment name="myjar1.jar">

    <dependencies>

      <module name="deployment.myear.ear.myjar2.jar" />

    </dependencies>

  </sub-deployment>

</jboss-deployment-structure>

But I have still the same error.

Thanks in advance for any help,

[jaikiran]

What kind of jars are myjar1.jar and myjar2.jar? Plain library jars or are they deployments containing EJBs? If they are plain library jars then move them to a .ear/lib (create the lib folder if the ear doesn't have one). If they are EJB deployments, then you don't have to customize anything. The classes in those sub deployments should be visible to one another.

[jsebfranck]

myjar2.jar is a plain library jar. I moved it to .ear/lib and it works ! Thank you very much.

[jsebfranck]

By the way, are the EJB packaged in the war file available to other modules of the application?

[jaikiran]

jsebfranck wrote:

By the way, are the EJB packaged in the war file available to other modules of the application?

You'll have to explain what exactly you mean by available? The EJBs are exposed via JNDI so yes those can be looked up. If you are talking about the availability of the EJB interface classes outside of the .war, then if you package those interfaces within a jar and place it in the .ear/lib then those will be available to all components in that ear.