The problem is that you are serializing the handle and then transporting that back to the client rather than letting the transport layer do the serialization. This fails because the JRMPInvoker is not being replaced by its remote stub. Either pass the handle back to the client and let the rmi transport layer handle the marshalling of the RMI object or handle replacement of RMI objects as is done in org.jboss.ejb.plugins.SessionObjectOutputStream
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Marcus Redeker" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 09, 2002 11:22 AM Subject: AW: Re: [JBoss-dev] Bug: EJB Handle not deserializable > Is there any news on this? We would really like to move to JBoss3 but this > is a showstopper. Maybe the problem is just the Base64 encoder we use > to serialize the EJB handle into a String. But I do not know where to > look. Maybe somebody can give me a hint. > > Thanks, > > --Marcus ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
