The problem with this class is that it't not a javabean-compatible class, and I can't do anything about that. Having the BeanSerializer here is not an option. The type mapping as I have it is like this:
This works so far, since I can actually generate output with the Serializer. There is a new problem on the horizon: adding SOAPHeaders during serializing does NOT generate the desired headers, but also no exceptions are thrown.... This puzzles me... Anyone added headers during serialization?
Hi all, I am looking for a guide to tell me how to write serializers/deserializers for my complex java object. My class is too complex to be a JavaBean, so the BeanSerializer will not help me. I know org.apache.axis.encoding is the package to look at, but I am confused with all the interfaces and baseclasses that are offered there. Even looking at the sourcecode of the objects in org.apache.axis.encoding.ser didn't shed light on it... The documentation from AXIS on creating serializers/deserializers isn't much of a help... Anyone got some more info?? Thnx in advance
Thanks all for your answers... Conclusion: having synchronized in the method declaration does not break the interface contract. That's what I wanted to know... Thanks
A hashtable makes no gurantees about the order it stores it's keys/values. It doesn't need to, since the values are retreived by key, not by index. If you want a fixed order List, read about java.util.LinkedList