What is the best way to deploy several EJB jars that call each other? It appears that you have to have the home and remote interfaces either:
1) Packaged in the calling JAR
2) In the Classpath of JBOSS Application Server as
a) A single JAR which contains all Home and Remote Interfaces
b) A jar for each Home and Remote Interface
1) Does adding Jars to the classpath require server re-starts
2) Does modifying an existing jar -- cause potential problems if JBOSS caches the classes in that jar
What are the best practices for this architecture?
I have tried many days to master how to implement the external ejb reference before finding your post.
And your post help me so much and thank you very much.
It is hard to say , but i think the best way is
Pachaged in the calling JAR.
1.that means a Engineer change order(ECO) should be brought to software development process.