This is not possible!! you will have to use my patch if you want it to work?
 
Thanks,
Parikh, Pratik | Software Engineer | Cerner Corporation | (1)-816-201-1298 | [EMAIL PROTECTED] | www.cerner.com
 


From: Kasi, Anand [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 19, 2006 12:06 PM
To: axis-user@ws.apache.org
Subject: RE: Eliminating element with xsi:nil

Thanks Anne. I like the idea of adding a handler to the outgoing message. However, I thought Axis did not let you remove elements from the soap body. Do you have any code examples as to how I can remove an xml element that has xsi:nil = true from the soap body from the handler?

 


Thanks,

Anand

 


From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 19, 2006 10:21 AM
To: axis-user@ws.apache.org
Subject: Re: Eliminating element with xsi:nil

 

If you have defined the field as nillable="true" and you have not specified minOccurs="0", then the message would not be valid if you left out the element. There's no way to tell Axis to do something invalid.

I suggest that you add a handler to the outgoing message and transform it to remove the nil elements.

Anne

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

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: axis-user@ws.apache.org
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

 

 

CONFIDENTIALITY NOTICE

This message and any included attachments
are from Cerner Corporation and are intended
only for the addressee. The information
contained in this message is confidential and
may constitute inside or non-public information
under international, federal, or state
securities laws. Unauthorized forwarding,
printing, copying, distribution, or use of such
information is strictly prohibited and may be
unlawful. If you are not the addressee, please
promptly delete this message and notify the
sender of the delivery error by e-mail or you
may call Cerner's corporate offices in Kansas
City, Missouri, U.S.A at (+1) (816)221-1024.
---------------------------------------- --

Reply via email to