I haven't seen a response to your question yet so I'll take a crack at it even though I'm an Axis newbie.
It depends... The whole key to consuming web services whose contract is published via WSDL is that the manner in which the WSDL was created is not supposed to matter.
I've been using Axis' WSDL parser to deal with WSDL files generated by .NET and Glue as well as by hand... and the only failures I've had are a) on valid WSDL constructs that aren't yet supported by Axis or b) bad WSDL.
The answer to your question is based on whether Axis has correctly implemented the WSDL spec and whether the target consumer is using a toolkit that correctly understands the WSDL spec.
-----Original Message-----
From: XYZ ABC [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 24, 2002 10:05 PM
To: [EMAIL PROTECTED]
Subject: What is the procedures to develop web service with Axis
Hi,
I know a lot of messages been talking about this, but I still
little confused, so I ask again.
To develop web service with axis(beta2),
1. write an interface with methods you want to expose,
if the parameter (say, an array of Phone class), and you want it to
be INOUT mode, then you need to create a Holder class for that,
and use that as the type for that parameter.
2. use Java2WSDL to generate WSDL file.
3. use WSDL2Java to generate All java src files.
My question would be, if use Holder class as type for the parameter,
then the genreated WSDL file will have type called PhoneArrayHolder,
and that is an container for Phone[], but will other soap implementation
client (.NET) understand this type by looking at this WSDL file?
Thanks
netatta
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
