What I didn't see was where I could provide my own Registry.lookup(String), or configure such a thing, to actuallyYou don't! You just create a proxy-binding inside of the jboss.xml or standardjboss.xml.
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).
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.
Before I crashed last night (er, this morning), I whipped
up a quick ProxyRegistry that does most of that. I never quite got it to work, though--I think I need a little better
understanding of what/when things actaully get marshalled to
the client JVM...details :-) Of course, I'd rather not have
to learn a thing and just tell something to go do it :-)
I think you're making it too complicated.
I think you're looking in the wrong spot. You just need to write a simple little interceptor and code to decide "is this one of the calls I want to proxy". Bind it to either your container-configuration or your jndi-name with a proxy-binding.I'm going to spend a couple of hours today, poking at this ProxyRegistry bit I have here, and see if I can get it working, because it is only a handful of code so far. If I don't get it working...another weekend.
Of course you could just do everything in JBoss and then you can use RMI/HTTP :-P
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
