I have a very complex object that I am trying to communicate between server and client. I have used the example in section 3. "Transporter sample - JBoss serialization" as my guide. If I return a null value it works fine. However if I try to return a real object I get a complex serialization error:

org.jboss.serial.exception.SerializationException at org.jboss.serial.persister.PrivateWritePersister.writeData(PrivateWritePersister.java:82) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:72) at org.jboss.serial.objectmetamodel.DataContainer$DataContainerOutput.writeObject(DataContainer.java:131).....

Sorry for the delay (been working on getting out the next release). I am a little lost as to the changes you've made. Would it be possible to send the source to the chagnes you've made (tom@jboss.org) and I'll look into it. I do know that we fixed a bug where we were looking at the type of the object passed and not it's declared interface, which was causing a limitation (although does not seem to be what you are seeing).

I think I figured out the problem I was having. There appeared to be two issues. The first being that I didn't have empty constructors (i.e.,public x (){}) for some of the variables that were being serialized. The second problem was that some of the constructors of variables being serialized were actually trying to use the main object that I was trying to ship. This wasn't a problem on the server since they were instantiated after the object was created. But on pulling them over this caused a recursive instantiation of the main object (which was suppose to be a singleton).

I now seem to have everything working using the 1.4.0 beta version. I will continue to test and report back any problems.