Hi

I recently spent quite a few hours searching for a strange bug that caused data to be mangled when I transferred it from a server to a client using Axis in both ends. I found that the error was caused by my bean. I had declared a constructor for the bean, which means that the default void constructor was no longer available. The result was that when a bean having two String fields was deserialized it ended up with the value of the first string field as the value of both. This problem could easily be fixed be either removing the constructor I had added, or just adding the default constructor back in.

But to me this seems like a bug, shouldn't axis report that it is unable to properly deserialize the bean? It seems like the deserializer tries to be smart and forgiving, but as is so frequently the case with smart code, the result is just wrong.

I hope this description explains the problem in enough detail, if not I can post some code, please let me know.

And thanks for developing a great product!

Andr� N�ss

Reply via email to