>
Hey,
Sasha I am not 100% sure but I think that:
> The problems
> ============
> I seem to have problems to serialize the ContainerRemote objects in my MBEAN
> hashtable
> structure. I get "java.rmi.MarshalException: Invalid remote object"
> exception. Do I need to take particular action to serialize this class?
>
> In fact, I guess the problem is much more in my understanding of the whole
> picture: In the proxy, where is the reference to the distant RMI container
> when communicating between distant JVM? (see *** above)
>
>
your problem stems from the fact that you have to , in your writeExternal
implementation of StatelessSessionProxy, include the list of all container remotes not
only one as it is now.
Have you done this?
> This method in GenericProxy:
>
> public void writeExternal(java.io.ObjectOutput out)
> throws IOException
> {
> out.writeUTF(name);
> out.writeObject(isLocal() ? container : null);
> out.writeLong(containerStartup);
> out.writeBoolean(optimize);
> }
>
> make me think that if we are not local, the container is not seralized. How
> is this possible? how can then the proxy, when arrived on the client side,
> determine where to direct its calls? I think I am not to far of something
> working but my ideas are not that crystal clear now... (and it is the first
> time I dig in JBoss code)
>
client proxy does make a check in invoke, it does isLocal() thingy and calls directly
over locally available reference to JRMPInvoker (implements ContainerRemote) or if it
is not local makes the call across the wire using stub of JRMPContainerInvoker.
HTH,
Vlada
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
