On Tue, 16 Oct 2001 07:04, Peter Royal wrote: > When I make an RMI call to my exported block, the first method with the > requested calling signature is executed, not the requested one. For > example, in my Remote interface I have: > > void registerClientNotification(RMIClientNotification > clientNotification) throws RemoteException; > > boolean isUserValid(String username, String password) throws > RemoteException; > > String getUserResource(String username, String resource) throws > RemoteException; > > > Calls to registerClientNotification work 100% of the time, its the only > method with that signature. > > However, whenever I call getUserResource, isUserValid is executed on the > server. Naturally this is throwing exceptions because the arguments aren't > correct. If I look at the stack trace on the callee side, it is calling the > correct method in the generated stub. Something is being lost in transit. > *ANY* call to a method that takes 2 string arguments is being directed to > isUserValid on the Phoenix side.
Now thats a hair curler ! ;) > I'm *REALLY* stumped. I searched the list archives and the only RMI-related > troubles I saw were relating to the ftp server component and exporting > stubs. I tried changing the code where I bind to the registry to match that > more, but no luck. > > I know Phoenix does some internal magic with proxies, etc. I don't know if > that may be part of the problem. Any thoughts/ideas would be greatly > appreciated. Thanks! I have a sneaking suspicion that it is to do with the proxy generation. (At least this would make sense if you were exporting one block from another block and RMI used reflection to generate messages). I will try to fix it tonight so that you can disable this - however some recent changes have gone through that may need alterations - so if not today perhaps tomorrow or the next day - If I forget remind me ;) -- Cheers, Pete *------------------------------------------------* | You can't wake a person who is pretending | | to be asleep. -Navajo Proverb. | *------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
