I agree with Glen that you should use an abstraction: at the very least you want to support both WSDL and XML Schema.
Anne > -----Original Message----- > From: Glen Daniels [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 20, 2002 8:37 AM > To: '[EMAIL PROTECTED]' > Subject: RE: WSDL Aware Runtime > > > > IMO, the Axis engine desperately needs a "service metadata" > abstraction, which I've been making noises about for a long time. > > I don't think this should be tightly bound to WSDL, though I do > think we should clearly be able to read WSDL into a > ServiceDescription (assuming that's what it gets called) and > write a ServiceDescription out as WSDL. The reasoning here is : > 1) the engine has a lot of uses for this data even in situations > where actual WSDL isn't required. 2) the WSDL data structures > aren't the most efficient way to deal with this stuff. 3) WSDL > is likely going to change at some point in the next year or so as > the ws-desc group works on it - I think we can do a good job with > defining clean abstractions around what we want, and then map > that to whichever version of WSDL we're using in the future (as > well as WSDL 1.1 for backwards-compatibility). > > I would be happy to help work on this. > > --Glen > > > -----Original Message----- > > From: R J Scheuerle Jr [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, February 19, 2002 1:53 PM > > To: [EMAIL PROTECTED] > > 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) > > >
