Understanding SimpleDeserializer encountered a child element, which is NOT expected messages

[Maxwell Grender-Jones <ma...@mxtelecom.com>]

I have set up a service, with a custom written deploy.wsdd file (as I do
not have a wsdl, and JAVA2WSDL does not correctly decode my java
classes).

When I call my service, I get 

faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: org.xml.sax.SAXException: SimpleDeserializer encountered a
child element, which is NOT expected, in something it was trying to
deserialize.
 faultActor:
 faultNode:
 faultDetail:

back from Axis. Is there any way of discovering exactly which element
had the unexpected child? Or alternatively, is this a common error, and
what should I look at again? I have checked all the typemappings, and I
think they are correct (although if told that this is the only way such
an error could occur I'll go through them again!)

Thanks in advance

Max

-- 
Maxwell Grender-Jones   <ma...@mxtelecom.com> 

Re: Understanding SimpleDeserializer encountered a child element, which is NOT expected messages

[Maxwell Grender-Jones <ma...@mxtelecom.com>]

Managed to find the problem: I had the style set to document (in my
wsdd), when it should have been document.

i.e. <service ... style="document" ...> -> <service ... style="rpc" ...>

Max
On Thu, 2004-07-01 at 13:39, Maxwell Grender-Jones wrote:
> I have set up a service, with a custom written deploy.wsdd file (as I do
> not have a wsdl, and JAVA2WSDL does not correctly decode my java
> classes).
> 
> When I call my service, I get 
> 
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>  faultSubcode:
>  faultString: org.xml.sax.SAXException: SimpleDeserializer encountered a
> child element, which is NOT expected, in something it was trying to
> deserialize.
>  faultActor:
>  faultNode:
>  faultDetail:
> 
> back from Axis. Is there any way of discovering exactly which element
> had the unexpected child? Or alternatively, is this a common error, and
> what should I look at again? I have checked all the typemappings, and I
> think they are correct (although if told that this is the only way such
> an error could occur I'll go through them again!)
> 
> Thanks in advance
> 
> Max
-- 
Maxwell Grender-Jones   <ma...@mxtelecom.com> 
http://www.mxtelecom.com/ +44 (0)845 6667778 

Technical support    <su...@mxtelecom.com>