I have a jar that contains many EJBs and I need to access those from multiple WARs. I'm trying to figure out the best way to package and deploy these to a single app server.
Currently, I deploy each WAR individually with each having a dependency on the common EJB jar, but this seems to be incredibly inefficient (memory-wise et al) as there are separate JNDI bindings for each application.
I've also tried packaging these WARs in an EAR but this doesn't seem to change anything.
Does this make any sense? How can I make sure that the common EJB jar is not "deployed" multiple times (once for each WAR that depends on it)?