Is there any way to speak to a session bean from a remote client without putting the JBoss client jars in the remote VM's classpath?
I am essentially writing a plug-in monitoring application that will live in the same VM as third party web application, and I want to avoid creating classpath conflicts. Specifically having to do with using jar files that may cause a conflict with jar files used by the third party app (perhaps in the case where the web app is acting as a remote client to JBoss 2.4 and my plug-in is talking to JBoss 3.0).
2.4 and 3.0 use entirely different client proxies
and client/server RMI implementations.
The only way you could get this to work would be
to partition your class space using different
classloaders so the two sets of classes cannot see each