Originally posted by Sivasundaram Umapathy:
The code would have worked because the server implemented a protocol which understood java casting but the code might not be portable to another container.
Originally posted by Andres Gonzalez:
The code works and they gave me the explanation of why they didn't use it. Before posting the answer, I'd like to know your opinions of why it worked, or why PortableRemoteObject couldn't be use (if that was the case ).
Originally posted by Andrew Monkhouse:
Now I don't know if Andres' code is faulty or not, but this is not what he had. Andres is showing two parameters (the Object and the Class) as though it was within a call to PortableRemoteObject.narrow(). So this just looks wrong.
Well you have my opinion on why my code above would work, but not why your code would work. Care to comment on whether your code is really correct (in which case I suspect you are hiding something from us (can't trust these Queenslanders ))
[ October 31, 2003: Message edited by: Andrew Monkhouse ]
Originally posted by Anselm Paulinus:
Enough of the hide and seek game.
What was the reason for not using portableRemoteObject.narrow()
I've been trying to find documentation on when this class was added, but can't find the @since tag.. If anyone knows please let me know; I'm still not satisfied with their response...