Can you accomplish this if you are using RPC-style Web Services as opposed to using Castor or does Castor fit into any RPC framework?
-----Original Message-----
From: Richard Martin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 06, 2004 2:18 PM
To: [EMAIL PROTECTED]
Subject: RE: SimpleDeserializer Error

If it's the deserialiser that's at fault then you can easily change it. I'd recommend downloading a copy of Castor (www.castor.org) and using it to do all the deserialisation.

In fact there's a developerworks article on how to do this here:

 

http://www-106.ibm.com/developerworks/library/ws-castor/

 

Give it a try; your mileage may vary - if the problem isn't the serialisation mechanism then this may not help.

 

Regards,

 

Richard

 


From: Pani, Gourav [mailto:[EMAIL PROTECTED]
Sent: 06 January 2004 18:55
To: '[EMAIL PROTECTED]'
Subject: RE: SimpleDeserializer Error

 

Is there some sort of a workaround to this?

-----Original Message-----
From: Richard Martin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 06, 2004 1:55 PM
To: [EMAIL PROTECTED]
Subject: RE: SimpleDeserializer Error

Yes, this appears to be a bug:

 

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17484

 

And there was another email about it not 3 or 4 weeks ago: http://www.mail-archive.com/[EMAIL PROTECTED]/msg16191.html

 

It seems that the deserialiser has problems deserialising arrays of custom objects, but that's just a first glance.

 

Regards,

 

Richard

 


From: Pani, Gourav [mailto:[EMAIL PROTECTED]
Sent: 06 January 2004 18:10
To: '[EMAIL PROTECTED]'
Subject: SimpleDeserializer Error

 

The following is the error I get when I post to a service. 

org.xml.sax.SAXException: Error: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.

 

My transaction sends an array of a serializable object and the construction of the object is consistent with the WSDL.  Has anyone else encountered this problem?

 

Thanks.

 

Reply via email to