godcomplex
Programmer
I have a rmi server and client. Client A (an applet) sends an object to the rmi server for storage in memory (a hash table), and returns a key for later retrieval. Client B (a servlet) uses that key to obtain the object from the server, and then calls a method to remove the object from the server's hash table.
The issue is, the object that I am passing back and forth for storage, is a CORBA object (ie, extends org.omg.CORBA.portable.IDLEntity). Now this alone seemd to work out fine, but the interface was altered and now we have a CORBA holder class wrapping the original, and I always get an UnMarahalling Exception. I am still sending the actual object, not the holder class.
From my experience in the past I know that I always had to implement Serializable, but in this case I figured a CORBA object would do the trick. Any thoughts on this?
-gc "I don't look busy because I did it right the first time."
The issue is, the object that I am passing back and forth for storage, is a CORBA object (ie, extends org.omg.CORBA.portable.IDLEntity). Now this alone seemd to work out fine, but the interface was altered and now we have a CORBA holder class wrapping the original, and I always get an UnMarahalling Exception. I am still sending the actual object, not the holder class.
From my experience in the past I know that I always had to implement Serializable, but in this case I figured a CORBA object would do the trick. Any thoughts on this?
-gc "I don't look busy because I did it right the first time."