In this case, I’m on a RedHat system, what I can’t figure out is how it is getting put in as a value to begin with. If it is on my end, how can I stop it? The message schema provided by the server looks like:
<xs:element minOccurs="0" maxOccurs="unbounded" name="MonitorSite" nillable="true" type="MonitorSiteOrder"/>
<xs:attribute name="siteId" type="xs:int" use="required"/>
[mailto:email@example.com] On Behalf Of Leo Lapworth
Sent: Friday, February 05, 2010 3:53 AM
To: Langston, James
Subject: Re: [Soaplite-devel] xsi:nil ?
On 4 February 2010 22:55, Langston, James <James.Langston@compuware.com> wrote:
<MonitorSite xsi:nil=”true” siteId=”330”/>
I can't tell you how to stop it I'm afraid.
It is standard that if the element has no value then this attribute is set (.Net also adds it by default), so I would suggest it would be better to solve the issue on the parser side (e.g. where this data is being sent to) to allow this - if at all possible.