The components are not serializable and why would you want to include an extra network hop on every db access?
Set up a datasource in every vm you need one.
I have a complexe application running on several machines which I try to migrate on JBOSS2.4.4 and Tomacat Catalina 4.01.
Two process of the application run under a JVM and do not need neither JBOSS nor Tomcat. But these two process require DBMS access.
Web and ejb parts of the application are configured under JBOSS +Tomcat Catalina.
The idee is use the Datasource JNDI name binded by JBOSS in one machine from an other machine without starting a second JBOSS server.
Do you have distributed transactions spanning several of your servers/vms? Do you need a transaction manager on the non-jboss nodes?
Why not set up micro-jbosses on the "non-jboss" machines that include naming and db support, and the tx manager if you need it, and nothing else, and run your apps on these nodes as mbeans in jboss?
If you do need distributed tx use Tyrex rather than the default tx manager.
I agree for this solution.
I will start my processes under micro-jbosses with Tyrex as transaction Manager.
Thanks a lot.