EJB3.1 Application Packaging

[Naren Chivukula]

On page 10-93 (Enterprise Java Beans 3.pdf by Frits), we have application.xml like this -

<application>
<display-name>app1</display-name>
<module>
<web>
<web-uri>app1Web.war</web-uri>
<context-root>app1Web</context-root>
</web>
</module>
<module>
<ejb>app1EJB.jar</ejb>
</module>
<module>
<java>app1EJBClient.jar</java>
</module>
</application>

1. I believe the <java> module above is optional as we already defined in the app1EJB.jar/MANIFEST.MF Class-Path entry for app1EJBClient.jar file.

2. If we had to provide the above module in the application.xml, then app1EJB.jar/MANIFEST.MF Class-Path entry for app1EJBClient.jar file becomes optional. This is because of EAR classloader is shared across all the modules.


Please correct my understanding.

[Frits Walraven]

Naren Chivukula wrote:
1. I believe the <java> module above is optional as we already defined in the app1EJB.jar/MANIFEST.MF Class-Path entry for app1EJBClient.jar file.

Yes, you are right! It seems my IDE added that when I created the ejb client project. I never noticed it, thanks, I will change that.

Regards,
Frits

[Naren Chivukula]

Thanks Frits.