Right. you only needed to modify the JBoss box (proxy), but it sounds
like that is out of your control?
Brent Verner wrote:
[2005-03-06 10:36] [EMAIL PROTECTED] said:
|
| > What I didn't see was where I could provide my own
| >Registry.lookup(String), or configure such a thing, to actually
| >pickup the "real" remote object to do the Proxy/InvocationHandler
| >dance with (from a different RMI server). Also, I didn't see
| >where any InvocationHandler return value would be checked for
| >being a Remote object (and needing to be proxied).
| >
| >
| >
| You don't! You just create a proxy-binding inside of the jboss.xml or
| standardjboss.xml.
|
| I wouldn't use JBoss to lookup the other server's stuff. I'd just do
| whatever you'd do from a client inside of the jboss interceptor.
The problem is that both ends of the RMI are a "black box".
I can't modify either the server or the client. I have zero
access to the RMI server machine and the only control I have,
is the configuration on the client to use an alternate server.
The code on the client that does Naming.lookup(...) is not
something I can change. I'd love to know the right (simpler)
way to have solved the problem, because I had a hell of a time
caching the Remote object successfully in the proxy...
| Of course you could just do everything in JBoss and then you can use
| RMI/HTTP :-P
My life wouldn't be so easy :-)
cheers.
Brent
_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org
_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org
