Another exception... Serializing inner classes

Question

Basically, I am tesing class dynamic loading, which I am failing to do till now using codebase within the local system. This was my original question,,, you can see it here http://forum.java.sun.com/thread.jspa?threadID=581979&tstart=0
which I did not solve as of yet.
However, this is a new question:
Does this error look nice? am I making a mistake when serializing and returning an object of an inner class by a remote call?? I have this code in the server class:
public Message getMessage()throws RemoteException{
return new MyMessage();
private class MyMessage implements Message{
//code
}Clinet class:
Message message=server.getMessage(); //generates ExceptionException :
java.lang.ClassCastException: cannot assign instance of $Proxy0 to field Server$MyMessage.this$0 of type Server in instance of Server$MyMessage
     at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:1977)
     at java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1157)
     at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1918)
     at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
     at sun.rmi.server.UnicastRef.unmarshalValue(UnicastRef.java:290)
     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:139)
     at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
     at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
     at $Proxy0.getMessage(Unknown Source)
     at Client.main(Client.java:30)
thank you very much...

Answer 1

I believe I need to have a better design as you are
suggesting...
I want to have a set of Remote interfaces that can be
implemented by different ways. These interfaces are
then distributed for other developpers. Assuming it
is a chat program where clients send Messages to
other clients through a server, I would like to have
each client implement his own RemoteClient in a way
that suits him using Callbacks. Serializing a class
that implements Message can be used to have it as
means to communicate. Dynamic class loading is then
used to get the classes for different implementation
of Message that circles the clients.
Two pieces definitely. The message which is of the group that says "please do this" and the functional part which is "for a given message do this".
There are probably other parts as well.
In that form, I wanted to test serializing anonymous
Messages, but it did not work because the enclosing
class will also be serialized (if it implemented
Serializable of course) or would throw an exception
if it does not implement it like the one in the
questions above as I have learned. Even if Inner
classes are used it still will not work. Only normal
classes, or static inner classes would work.
If the "functionality" is truly general then there probably should be only one message. It would have attributes something like this...
- Function request name
- List of function parameters.
- List of function results.
After getting answers to my problems, as always, I
end up meeting new problems, I have these questions:
How to serialize Actions(AbstractActions,
ActionListeners)??What is an "action" and why do you need to serialize it?
If it is a message then make it a message.
How can I serialize this:
button.addActionListener(new ActionListiner(){
public void actionPerformed(ActionEvent e){You don't. At least not in terms of your above problem description.
This code is gui code. It is neither a message nor a "function". You don't send guis somewhere else.
/// or this
button.addActionListiner(new MyAction());
static class MyActionExtends implements
ActionListener{
public void actionPerformed(ActionEvent e){
//code
}Again you don't. I suspect you are mixing functionality.
Your gui should talk to your message layer. You might even have a gui layer, a message layer and a message-gui layer.
How can I overcome this problem?? Sending a GUI
through RMI looks very nice!!! with Buttons that
perform Remote Actions!!
Based on your system description above it is simply wrong.
Maybe there is more to your system though.