>Archive Index
>microsoft.public.xml Archive Home
>Recent entries

>Thread Prev - REPOST:
>Thread Next - Re: REPOST:

Re: REPOST:

From: "Joe Fawcett" <joefawcett@---------.------>
To: NULL
Date: 12/6/2006 1:29:00 PM


<teddysnips@h...> wrote in message 
news:1165398632.427606.237840@f......
> In the class declaration of a web service that I've just picked up for
> maintenance:
>
> <Obsolete("Superseded by OrderPaymentElements")> Public PaymentType
> As OrderPaymentType
>     Public OrderPaymentElements As OrderPaymentList
>
> Apparently there's a problem with the generated SOAP.  This is what
> the client said:
>
> "Server was unable to read request. --> There is an error in XML
> document (1, 1553). --> '0' is not a valid value for OrderPaymentType"
>
> Looking at the request that is the position of the PaymentType element
> in the soap document."
>
> Can anyone tell me what possible purpose the <Obsolete tag has?  Are
> there any reasons not to use <XmlIgnore()> instead?  More worryingly,
> why is the server barfing?
>
> DISCLAIMER:  I'm new to this and it's a pretty complex, and completely
> undocumented application.  Aren't I the lucky one?
>
> Thanks
>
> Edward
>
XmlIgnore and Obsolete are two very different attributes, the former says do 
not include this property in XML serialisation, the latter is marking the 
property as obsolete.
Sound to me like the WSDL schema has payment type down as an enumeration or 
the like with 0 an invalid choice.
Can you show the schema?


-- 

Joe Fawcett (MVP - XML)

http://joe.fawcett.name

>Thread Prev - REPOST:
>Thread Next - Re: REPOST:

>Archive Index
>microsoft.public.xml Archive Home
>Recent entries

Altova Mailing List Archives

Re: REPOST: