@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
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 Ax
, January 19,
2006 9:19 AMTo: axis-user@ws.apache.orgSubject: RE:
Eliminating element with xsi:nil
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
,
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
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
: axis-user@ws.apache.orgSubject: 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
