In order to be able to switch JDBC drivers, the application using the JXDBC proxy driver must be unaware that it uses JXTA.
It must be possible to run more than one JXDBC application without having to configure more than one peer on the client side of the proxy.
The server side of the proxy must be able to service more than one database.
This leads to the following architecture.
> <-communication-> <-JXTA-> >
A usual solution for two java applications to communicate is either to use sockets or RMI.
I have chosen RMI.
Why RMI? Since JXDBC is a proxy for JDBC driver