We have multiple applications deployed in the same app server in different .ear files that need to talk to each other. The current solution is a .properties file in the parent classpath that defines the properties needed to look up an EJB in the other .ear. It would be much faster and less code if we could just grab a hold of a POJO.
What I would like to do is place a Spring context file in a parent classpath that one .ear could read and gain access to classes in the other .ear. I will admit I have not tried this because I am more in the theoretical thinking stage at the moment, but I do not see how app A could see the classes of app B.
We could, of course, define a bean in the parent classpath that is a LocalStatelessSessionProxyFactoryBean, or use Hessian. Is this really the only solution? Does anybody have any good ideas for this scenario?