[jboss-dev-forums] [Design of POJO Server] - Re: Missing org.jnp.server.NamingServer_Stub

[adrian@jboss.org]

It is using the dynamic proxy which you can see from the logging
when it binds the stub:


  | 2008-11-21 13:06:31,807 DEBUG [org.jboss.naming.Naming] (main) Creating NamingServer stub, theServer=MBeanProxyExt[jboss:service=NamingBeanImpl],rmiPort=1098,clientSoc
  | ketFactory=null,serverSocketFactory=org.jboss.net.sockets.DefaultSocketFactory at e048aaa4[bindAddress=/127.0.0.1]
  | 2008-11-21 13:06:32,082 DEBUG [org.jboss.naming.Naming] (main) NamingServer stub: Proxy[Naming,RemoteObjectInvocationHandler[UnicastRef2 [liveRef: [endpoint:[127.0.0.1
  | :1098,org.jboss.net.sockets.DefaultSocketFactory at e048aaa4[bindAddress=/127.0.0.1]](local),objID:[0]]]]]
  | 

My guess is that it can't deserialze the proxy because there is a new interface not in 4.2.x
i.e. org.jnp.interfaces.NamingEvents
so it is falling back to trying to use the stub?

Which way around is this test? It's not clear from the above description.
The old stub should be available in 4.2.x without the new interface methods?


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191238#4191238

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191238