Could you send me the WSDL ?. It seems that wsdl2ws should work with it. --- Susantha.
> -----Original Message----- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Friday, May 07, 2004 5:40 PM > To: [EMAIL PROTECTED] > Subject: RE: Why use WSDL? > > Turn your hashmap into an array. > > First rule of interoperability -- do expose collections (List, Map, etc) > through your interface. > > Anne > > -----Original Message----- > From: Dorner Thomas [mailto:[EMAIL PROTECTED] > Sent: Friday, May 07, 2004 2:54 AM > To: '[EMAIL PROTECTED]' > Subject: AW: Why use WSDL? > > Some problems by using wsdl: > > I have a auto generated wsdl (java2wsdl axis)- A friend wanna use > this wsdl by by axis c++ (wsdl2ws) to generate the classes. > > My wsdl contains a Hashmap - see example: > > <wsdl:types> > - <schema targetNamespace="http://xml.apache.org/xml-soap"; > xmlns="http://www.w3.org/2001/XMLSchema";> > <import namespace="http://schemas.xmlsoap.org/soap/encoding/"; /> > - <complexType name="mapItem"> > - <sequence> > <element name="key" nillable="true" type="xsd:string" /> > <element name="value" nillable="true" type="xsd:string" /> > </sequence> > </complexType> > - <complexType name="Map"> > - <sequence> > <element maxOccurs="unbounded" minOccurs="0" name="item" > type="apachesoap:mapItem" /> > </sequence> > </complexType> > </schema> > </wsdl:types> > > > But the tool can�t handle the type Hashmap - exception: > > org.apache.axis.wsdl.wsdl2ws.WrapperFault: unregisterd type > {http://xml.apache.org/xml-soap}Map refered > > > So, not even axis can handle their own wsdl? > Their is also a Hashtable in c++!? > > Have somebody an idea to solve this problem? > > Thanks Thomas > > > > > -----Urspr�ngliche Nachricht----- > Von: Hittesdorf,Michael [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 6. Mai 2004 17:43 > An: [EMAIL PROTECTED] > Betreff: RE: Why use WSDL? > > > > Some good reasons to use WSDL: > > 1. WSDL aids interoperability. You can post your WSDL to a directory and > any Web Services developer in any technology (Java, .NET, etc.) will > have everything they need to build a client to invoke your service > (assuming it conforms to established conventions/standards, such as > WS-I) > > 2. WSDL is more expressive than Java alone. With WSDL I can specify > message payloads, invocation styles (RPC or document) and encoding, as > well as endpoint addresses. > > > 3. WSDL is a required artifact for many testing tools, Web Services > frameworks, and service management products. Without WSDL, you can't > take advantage of these technologies > > 4. WSDL is a standard. Though Axis lets you develop 'Web Services' > without WSDL, this is not the accepted approach. You are better off > conforming to standards and conventions when building software that > potentially needs to communicate with the outside world. > > 5. WSDL assists in portability. If you want to switch from Axis to > another Web Services toolkit, you will have a definition of your service > from which to start. > > > > There are probably other reasons but these are what comes immediately to > mind. > > Mick > > > -----Original Message----- > From: Robert Mecklenburg [mailto:[EMAIL PROTECTED] > > Sent: Thursday, May 06, 2004 9:17 AM > To: Axis Users > Subject: Why use WSDL? > > > I'm new to axis and web services and I have a basic question. > > Why bother with wsdl? > > Here is a service: > > public class Service > { > public String doSomething(String name) throws RemoteException > { ... > return result; > } > } > > > Here is a client: > > public class Client > { > public String add(String name) throws AxisFault > { > Call call = new Call(getServerURL() + "/Service"); > return (String) call.invoke("doSomething", new Object[] {name}); > } > } > > > What could be simpler? When I started with axis I wrote interfaces, > then ran Java2WSDL, then generated client and server stubs with > WSDL2Java. For a similar service I wound up with 7 classes and 200 > lines of code -- all of which appears to be pointless. I can do the > same thing with 0 extra classes and two lines of simple java if I > avoid the WSDL. > > > So I'm trying to figure out what I'm missing. Obviously someone > thinks WSDL is worth all the extra obscurity, code bloat, and build > complexity. Please tell me your reasons. > > > Thanks! > -- > > Robert > > E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and > any > attachments are intended solely for the > > addressee(s) and may contain confidential and/or legally privileged > information. If you are not the > > intended recipient of this message or if this message has been addressed > to > you in error, please > > immediately alert the sender by reply e-mail and then delete this message > and any attachments. If you > > are not the intended recipient, you are notified that any use, > dissemination, distribution, copying, or > > storage of this message or any attachment is strictly prohibited.
