-
1. Re: AS7 "Failed to define class" error with jboss-deployment-structure configuration
jaikiran Dec 1, 2011 2:26 AM (in response to jsebfranck)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.
-
2. Re: AS7 "Failed to define class" error with jboss-deployment-structure configuration
jsebfranck Dec 1, 2011 4:11 AM (in response to jaikiran)myjar2.jar is a plain library jar. I moved it to .ear/lib and it works ! Thank you very much.
-
3. Re: AS7 "Failed to define class" error with jboss-deployment-structure configuration
jsebfranck Jun 22, 2012 2:53 AM (in response to jsebfranck)By the way, are the EJB packaged in the war file available to other modules of the application?
-
4. Re: AS7 "Failed to define class" error with jboss-deployment-structure configuration
jaikiran Jun 22, 2012 2:57 AM (in response to jsebfranck)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.