Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <43F99324.4030903@multicom.co.uk>
Date: Mon, 20 Feb 2006 10:00:04 +0000
From: Tim R J Langford <tim@multicom.co.uk>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
MIME-Version: 1.0
To: axis-user@ws.apache.org
Subject: Re: How to not send nillable="true" for null elements in a SOAP
 message
References: 
 <8A1F9FA924FBDB47A53086AA86BBDDA3017DEB56@sgtulmsp03.Global.ad.sabre.com>
 <43F455D7.5080107@multicom.co.uk>
 <8A1F9FA924FBDB47A53086AA86BBDDA30E6328@sgtulmsp03.Global.ad.sabre.com>
In-Reply-To: 
 <8A1F9FA924FBDB47A53086AA86BBDDA30E6328@sgtulmsp03.Global.ad.sabre.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello All,

Is it a bug in Axis1.3 that WSDL with nillable="false" and 
minOccurs="0", still genrates a nilable="true" string on serialisation? 
Is there somewhere I can log this bug or enhancement?

I may be able to do this in work time. Where would I start with Axis1.3 
to add/alter the code to deal with this? WSDL2Java mainly generates 
beans and a few other files. How would the code to analyse the presence 
of nillable="true" in the schema and the unmarshalling of message 
objects fit together in the axis framework? some sort of variable set in 
the beans to indicate nillable should not be sent that is inspected on 
serilaisation; or some extracted supporting object that contains such 
information? Would this be a fairly simple task?

Thanks for you time,

Tim