Return-Path: Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list axis-user@xml.apache.org Received: (qmail 50979 invoked from network); 2 Jan 2002 16:09:31 -0000 Received: from unknown (HELO dnexchange.neonsoft.com) (208.213.207.253) by daedalus.apache.org with SMTP; 2 Jan 2002 16:09:31 -0000 Received: by DNEXCHANGE with Internet Mail Service (5.5.2653.19) id ; Wed, 2 Jan 2002 09:19:50 -0700 Message-ID: From: "Jack, Adam" To: axis-user@xml.apache.org Subject: RE: (De)Serialization of complex types AXIS alpha3 w/ WSDL4J Date: Wed, 2 Jan 2002 09:06:34 -0700 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 Thanks that is good info. I'll start there w/ that approach & that source. regards Adam -----Original Message----- From: Mark Young [mailto:mark@kamiak.com] Sent: Wednesday, January 02, 2002 9:12 AM To: axis-user@xml.apache.org Subject: Re: (De)Serialization of complex types AXIS alpha3 w/ WSDL4J Adam: The WSDL2Java utility (org.apache.axis.wsdl.WSDL2Java) does handle that WSDL you mention. I haven't done so, but if you need to figure out how to roll your own web service client, you might be able to look at the source for it. I guess you don't just want to construct a client the quick and easy way? I've had good success using WSDL2Java and then just filling in the classes it generates for me. Regards, ------------------------------------------- Mark Young, Kamiak Corp. XML Schema and Web Service Contract (WSDL) authoring software http://www.omniopera.com ----- Original Message ----- From: "Jack, Adam" To: Sent: Monday, December 31, 2001 6:12 PM Subject: (De)Serialization of complex types AXIS alpha3 w/ WSDL4J > All, > > I have been experimenting w/ AXIS alpha 3 & it's WSDL4J and I tried using it > to call the xmethods listing service (so I could get a list of other WSDLs > to go experiment with). [This was an attempt to "experience" varied WSDL > forms (.Net and others) and learn about it from a practical point of view.] > > I've learn a lot (through mild to medium pain) and not all that I'd hoped. > [See below for feedback]. > > It turned out that the first WSDL I chose had some complex types, and I > couldn't figure out how to work with these. The serialization example > (SerData.java) was helpful -- but seems "old style", and since I ended up > attempting to go javax.xml.rpc.* I could figure out how to add a > serializer/deserializer to do the job. > > My questions: > > * I could see how AXIS serializers/deserializers are tree builders/SAX > handlers --- but how to JAVX.XML.RPC ones work? Are these not the same? If > they are any samples? > * Do you think javax.xml.rpc.Service will return a > javax.wsdl.Definition [save me going to get it again] any time soon? > * Can I get "complex types" from the Service or Definition? > * If I am on the wrong track, how ought I work w/ complex types & > perhaps WSDL "introspection" w/ AXIS? > > FWIIW: This is what I was working with: > > http://www.xmethods.com/detail.html?id=23 > http://www.xmethods.net/sd/2001/XMethodsListingsService.wsdl > > Note: I've told the folk at xmethods about their URI mismatch (WSDL > != deployed.) > > Thanks in advance for any help. > > regards, > > Adam