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
Again we can take care of this at the proxy (the one to JNP) level. I will
look into it, always wanted to
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Bill
|Burke
|Sent: Thursday, February 14, 2002 10:03 AM
|To: David Jencks; jboss-dev
|No, there is no requirement that objects be stored in serialized form.
great, I will try to do that at the client proxy level then. It will be a
great example of detached invokers and externalized client interceptors.
Fuck, I need client interceptors in a BIG way. I will move that up my list
I think we need to rewrite the service, it is in need of a big factorization
at this point.
Again I will try to do that with the new JBoss3.0 service/proxy
architectures. Stay tuned.
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of David
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
In my experience so far, Home's are looked up only once on the client and
cached, so I agree with you David. Proxies shouldn't be serialized into
JNDI.
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Jencks
Sent: Thursday, February 14,
Bill Burke wrote:
In my experience so far, Home's are looked up only once on the client and
cached, so I agree with you David. Proxies shouldn't be serialized into
JNDI.
I was looking at this recently while trying to work out whether JNDI has
anything to say about it itself. Isn't this done
I was looking at this recently while trying to work out whether JNDI has
anything to say about it itself. Isn't this done in the ProxyFactory
code? As far as I can see it just passes a reference to the EJBHome
object to the rebind function. Where does it get serialized?
In the jnp JNDI
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
David Jencks wrote:
On 2002.02.14 13:35:56 -0500 Luke Taylor wrote:
naming module, org.jnp.interfaces.NamingContext.rebind
I put the println in
if (!(obj instanceof Reference))
{
className = obj.getClass ().getName ();
// Normal object -
On 2002.02.14 15:12:26 -0500 Luke Taylor wrote:
David Jencks wrote:
On 2002.02.14 13:35:56 -0500 Luke Taylor wrote:
naming module, org.jnp.interfaces.NamingContext.rebind
I put the println in
if (!(obj instanceof Reference))
{
className =
11 matches
Mail list logo
