My Axis server was generating a fault with the dreaded:
"org.xml.sax.SAXException: SimpleDeserializer encountered a child element,
which is NOT expected, in something it was trying to deserialize."
For a while, I thought this had to do with the complex type the offending
method was returning. Af
m.
--
Tom Jordahl
Macromedia Server Development
-----Original Message-
From: Mitch Gitman [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 02, 2002 8:44 PM
To: [EMAIL PROTECTED]
Subject: deserializing nested complex types
I had come to realize (perhaps mistakenly) that I needed to use a cust
EMAIL PROTECTED]]
Sent: Monday, December 02, 2002 8:44 PM
To: [EMAIL PROTECTED]
Subject: deserializing nested complex types
I had come to realize (perhaps mistakenly) that I needed to use a custom
serializer/deserializer for a complex type that had another JavaBean
complex type as an element insi
Minor point aside from the larger issue of plugging in custom
deserialization. I notice that the Axis framework instantiates my custom
deserializer factory but then, rather than asking the factory for a custom
deserializer, just goes ahead and uses SimplerDeserializer anyway.
At 17:44 02.12.02
I had come to realize (perhaps mistakenly) that I needed to use a custom
serializer/deserializer for a complex type that had another JavaBean
complex type as an element inside it. You see, when my test Axis client was
querying the server, it was generating a fault with a stackTrace that began:
o
