That is a problem with JNP. JNP serializes everything by default. You must use the not serialized object to bypass the serialization.
One thing I would like to look into is to reimplement the JNP service with the new service architecture and custom client proxies of JBoss3.0 so we can leverage features such as not serializing in VM. This means we would show that 3.0 supports RMI invocation to any service through the JMX M-bus. Trivial I think, I will try to do it (as soon as I get my todo list of today down to 238 items) marcf |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of David |Jencks |Sent: Thursday, February 14, 2002 9:48 AM |To: jboss-dev |Subject: [JBoss-dev] Is it necessary to store Proxies in serialized form |in jndi? (jboss 3) | | |It appears that in jboss 3, cvs, proxies for home interfaces are being |bound into jndi as serialized, MarshalledObjects. Is this necessary? This |appears to result in deserialization on every jndi lookup. While this |speeds up remote access, it slows down local access. I think we want to |favor local access over remote access. | |Would using an ObjectFactory work for remote access? | |Is it possible to somehow use an ObjectFactory for local access and a |preserialized form for remote access? | |_______________________________________________ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
