This is how the jnp ipmlementation has been for quite a while, so its also how things work in 2.4. I believe there does have to be a MarshalledObject stored at the time of binding because this is where the context class loader is correct for annotation of the classes stored into JNDI and this is what controls what the RMI codebase that remote clients see.
A simple reference as well as the serialized form could be stored and the serialized form bypassed on lookup from a local client. Its on my list of changes to make to the jnp implementation. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: "jboss-dev" <[EMAIL PROTECTED]> Sent: Thursday, February 14, 2002 9:48 AM 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
