Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (athena.apache.org: domain of deepalk@gmail.com designates
 209.85.221.15 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=jphfzwL2e6ujsDJk+7q/bR3dHWAiRqVgBcH8dwNtW38yhZUtlMXPhiXYr0fKrl074G
         Ie82HeAIb8eCe1vV237Xf+Xxrp+OxXzdCeSf6hgR1ZVTk6NBQZSWxHK4dXjJMyrNhGXL
         yQe2cgVhbh2kOMAGwLOFcsvz1Y98NU0AKRF8Y=
Message-ID: <4942B20B.1070405@gmail.com>
Date: Fri, 12 Dec 2008 13:48:43 -0500
From: Deepal jayasinghe <deepalk@gmail.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Re: Looking into open issue 3364
References: <AE5F1332830D4EAC9780DCC575C22D78@IRANTHAPC>
	<49427410.40607@gmail.com> <4942AF6A.4090704@thoughtcraft.com>
In-Reply-To: <4942AF6A.4090704@thoughtcraft.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Glen,
>
>> As I mentioned in the JIRA, I did a local fix and get  that working,
>> however most of the java2wsdl and some runtime code generation tests
>> failed. So I did not commit the changes. My changes only involve in
>> SchemaGenerator, and it is very simple fix. Only thing is to make sure
>> you get the test cases working. Currently for any input type it sets
>> minoccurs to 0 , so you just need to change that to 1.
>
> So you're saying we shouldn't support optional parameters, and
> therefore we should be throwing an exception for missing parameters? 
> And we shouldn't be able to pass null values?  Hmm...
Well I was referring to generate WSDL to cope with RPC MR. I agree with
you, but to handle those we need to fix the RPC MR. So my suggestion was
to get what working right, and then address the improvements later.
>
> I think we should be able to be as expressive and simple as possible
> in making our schemas align with the Java structure - and supporting
> missing wire parameters which will become null values for Object types
> certainly seems reasonable toward that end.
Agreed. But if you put minoccurs=0 , that's mean it is possible that
parameter not appear in the request. Of course we handle nillable
correctly. In my understanding nillable and minoccurs are two different
things (please correct me if I am wrong)
>
> In other words, IMO we should support on the server side:
>
> Type        Result if missing    Schema
> ----------------------------------------------------------
> primitive    exception        minOc=1
+1, but we need to burn schema aware passing logic into RPC MR.
> Object        null            minOc=0
Nope, here we need to add additional "nillable=true" attribute for
complex types.
>
> Also, this way if the client wants to send a null there's a way to do
> it (don't include the param).
>
> This doesn't seem that hard to do, and I think it makes for nicer REST
> URLs and SOAP messages in some cases.
>
> Thoughts?
>
> --Glen
>


-- 
Thank you!


http://blogs.deepal.org