Return-Path: 
 <axis-dev-return-6482-apmail-xml-axis-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org
Received: (qmail 82340 invoked by uid 500); 19 Feb 2002 19:27:29 -0000
Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
list-help: <mailto:axis-dev-help@xml.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@xml.apache.org>
list-post: <mailto:axis-dev@xml.apache.org>
Delivered-To: mailing list axis-dev@xml.apache.org
Received: (qmail 82309 invoked from network); 19 Feb 2002 19:27:29 -0000
Message-ID: <079FD72E42C9D311B854009027650E6F0BCD68F7@xatl02.atl.hp.com>
From: "CHEN,SHIH-CHANG (HP-NewJersey,ex2)" <shih-chang_chen@hp.com>
To: "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
Subject: RE: WSDL Aware Runtime
Date: Tue, 19 Feb 2002 11:27:30 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

1. Current HP-SOAP does this. However, the 'WSDL-aware' feature, we 
called it 'WSDL-validation', should be optional/configurable. If 
'all' type information are NOT missing, wsdl MAY not be required 
to correctly process a request.

2. Instead of using wsdl, you could use introspection of the 
service impl class to figure out what type the param is. If this
is feasible/appropriate, then the purpose of setting WSDL-aware
is to validate request soap against the WSDL.

3. For your example:
	<echoParam>
		<param>123</param>
	</echoParam>

If the service impl overload the echoParam as following:
String echoParam( int i ) {
	return "integer";
}
String echoParam( String s ) {
	return "string";
}

And the correspond operations on wsdl is also overloaded. Then the 
type info still cannot be resolved from wsdl( and introspect. ).
I think a ambiguity exception/fault should be response in such case.


-chen



> -----Original Message-----
> From: R J Scheuerle Jr [mailto:scheu@us.ibm.com]
> Sent: Tuesday, February 19, 2002 1:53 PM
> To: axis-dev@xml.apache.org
> Subject: WSDL Aware Runtime
> 
> 
> I would appreciate some comments on the proposal to make the 
> runtime 'wsdl
> aware'
> 
> For example, if the following is recieved off the wire:
> 
> <echoParam>
>    <param>123</param>
> </echoParam>
> 
> There is no way to determine how to deserialize the data 
> because the type
> attribute is not specified.
> But if the runtime is 'wsdl aware' it could examine the wsdl 
> and determine
> the type of
> <param> and do the proper deserialization.
> 
> Making the runtime 'wsdl aware' would also allow axis to check xml
> instances coming over
> the wire against the format described in the wsdl.  I suspect 
> that other
> non-axis runtimes may
> already be doing this.
> 
> Making the runtime 'wsdl aware' would also eliminate the 
> extra information
> that is generated
> in the skeleton classes.
> 
> The serializers/deserializers would need to be changed to traverse the
> wsdl/xml during
> serialization/deserialization.
> 
> Has anyone given this any thought?
> 
> Rich Scheuerle
> XML & Web Services Development
> 512-838-5115  (IBM TL 678-5115)
>