• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

EJB3.1 Application Packaging

 
Naren Chivukula
Ranch Hand
Posts: 577
Java Notepad Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
On page 10-93 (Enterprise Java Beans 3.pdf by Frits), we have application.xml like this -



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
Creator of Enthuware JWS+ V6
Saloon Keeper
Pie
Posts: 2536
113
Android Chrome Eclipse IDE
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Ranch Hand
Posts: 577
Java Notepad Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Frits.


 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic