I have some experince with RMI, but none with jdbc... so take this with
appropriate amounts of NaCl....
The only thought I have is that the extra colons are throwing rmi, jdbc
or both. I'd try the following sequence:
If you have control over what the rmi name of the object is then get rid
of the colons... use / instead. i.e. rmi://horus/jdbc/postgresql/conrado
(If I were a betting man, my money would be on this one. :)
If you can try the client on the same machine as the seerver then drop the
name from the rmi url. (I assume that won't work in deployment, but might
lead to the culprit....)
If whoever parses the jdbc: url knows that the next part is rmi (i.e.
doesn't need to be told so, can assume it and pass on the url blindly)
then drop the "rmi:"; RMI doesn't need it. (I doubt this is an option.)
Good luck, hope this can help. -=Chris
<*> cabbey at rconnect dot com http://homepage.rconnect.com/cabbey/ <*>
Get it up, keep it up... LINUX: Viagra for the PC. ;) PGP Info: pgp.html
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12 http://www.geekcode.com
GCS$/IT/PA$ d(-) s++:+ a-- C+++$ UL++++ UA++$ P++ L++ E- W++ N+ o? K? !P
w---(+)$ O- M-- V-- Y+ PGP+ t--- 5++ X+ R tv b+ DI+++ D G e++ h(+) r@ y?
------END GEEK CODE BLOCK------
