Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Let’s say I have two ear file and one .jar file with an EJB that both of the EARs use. I want to do this because in some cases I might deploy one ear to an app server, but in others I might want to deploy both and I don’t want to create different ear file for each scenario.
How do I best package the “client” classes for the EJB? Using JBoss I can put them pretty much anywhere and it seems to work since it has a shared classloader. But I wonder what the official way to do this is?
Put the common ejb jar file in both ears. EAR’s are supposed to be standalone pacakages, with external setup via JNDI
When it comes to EAR’s, you don’t buy yourself anything but classloader problems when you try to “save space”, or “DRY” with jar files between them.