RE: Eliminating element with xsi:nil

Thu, 19 Jan 2006 07:20:10 -0800

Thanks for the tip. However, I do not have the option of changing the wsdl to include nillable=”false” and minOccurs=”0”. This is because our customers already are using client proxy which generated from the wsdl. I was wondering if there was a way to include new fields in the response, without impacting those customers who do not need the new functionality. Those who need the new functionality will regenerate from the new wsdl with new fields in it. Currently it does not work because it sees the new field come across in the response as <errorLevel xsi:nil="true"/> and obviously does not know what errorLevel is.

 

Is there any way of configuring Axis on the server side, to eliminate the xml elements from the soap response when xsi:nil is set to true?

 

Regards,
Anand

From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 6:27 PM
To: [email protected]
Subject: Re: Eliminating element with xsi:nil

 

Define the element as nillable="false" and specify minOccurs="0".

Anne

On 1/18/06, Kasi, Anand <[EMAIL PROTECTED]> wrote:

Hi All,

I am using Axis 1.3. Is there any way of eliminating the xml element from the soap message when the element 's xsi:nil is set to "true" .

Instead of

  

<advisory>

                    <advCondTextCode>Generic Error < /advCondTextCode>

                    <code>10 0</code>

                    <errorLevel xsi:nil="true"/>

                    <fullAdvisoryText xsi:nil="true"/>

  </advisory>

I want to see

   <advisory>

                    <advCondTextCode>Generic Error < /advCondTextCode>

                    <code>10 0</code>

  </advisory>

Thanks,
Anand

 

Reply via email to