There is a bug, which I have a fix for and will check in to the CVS tree shortly.
The stub still doesn't work however. It has to do with the document vs. rpc style, which we don't do the right thing. I believe you could use this service if you change the use to encoded in the WSDL and generate stubs... I am still looking at it, but no promises for a short term fix. :-) -- Tom Jordahl -----Original Message----- From: Brette, Marc [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 11:27 AM To: '[EMAIL PROTECTED]' Subject: RE: WSDL2Java problem with complex type ? It's still posiible there is a bug. It's a service I found on xmethods.(http://www.xmethods.com/ve2/ViewListing.po;jsessionid=UVEvYvEq3Vzh 2RNpUafIq-lX(QCcd0CRM)?serviceid=95) I tried to remove locally the "encodingStyle" parameter but still got the same problem. Thanks for your help. -----Original Message----- From: Tom Jordahl [mailto:[EMAIL PROTECTED]] Sent: 06 February 2002 16:45 To: '[EMAIL PROTECTED]' Subject: RE: WSDL2Java problem with complex type ? In looking at the WSDL, this is strange: <soap:body use="literal" namespace="urn:vgx-realtime" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; /> Why is their an encoding style listed when use=literal? Is this just a bug in the WSDL? I will still take a look at this. -- Tom Jordahl Macromedia -----Original Message----- From: Tom Jordahl [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 10:43 AM To: 'Russell Butek'; '[EMAIL PROTECTED]' Subject: RE: WSDL2Java problem with complex type ? The rpc/literal case isn't handled correctly by the emitter, as you discovered. This is mostly because we treat literal use in the manner that will enhance working with .NET. I'll try to take a look at what is going wrong with the stub signatures in this case. Perhaps it will be something simple to fix. JAX-RPC says we must handle the other three types: document/literal, document/encoded (which we don't explicitly deal with yet either) and rpc/encoded. This should be a matter of making sure we handle both switches independently, but it never seems to come out that simple. :-( -- Tom Jordahl Macromedia -----Original Message----- From: Russell Butek [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 8:48 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: WSDL2Java problem with complex type ? The soap:body in the binding says use="literal". This means that the outer layer - getRTQuote/getRTQuoteResponse - is stripped and the contents of the complexType are in the parameter list instead of the complexType itself, so nothing need be generated for the complexType. Now that that's explained, I have a question for Tom. This code is really meant for document literal, but this example is rpc literal (soap:binding style="rpc", soap:body use="literal"). Are we doing the right thing for rpc literal? I'm not sure what that means, myself. JAX-RPC doesn't address it. Russell Butek [EMAIL PROTECTED] "Brette, Marc" <[EMAIL PROTECTED]> on 02/06/2002 04:13:02 AM Please respond to [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: WSDL2Java problem with complex type ? Hi, I try to use WSDL2Java to generate stubs. The WSDL file defining the service is http://services.xmltoday.com/vx_engine/wsdl.vep/realtime.wsdl I tried to use the 02/05/2002 nighlty build, but no classes are generated for the complex types getRTQuote and getRTQuoteResponse, whereas they are used in the messages. However, WSDL2Java generate a vgx-realtime.StockQuotes which is a "member" of getRTQuoteResponse. I saw some related post on the mailing list archive that said it should work, so I wondered if this particular WSDL file would mess things. ------ The command I used to generate the stub is : java org.apache.axis.wsdl.WSDL2Java http://services.xmltoday.com/vx_engine/wsdl.vep/realtime.wsdl I copied here an extract of the WSDL file : <types> - <schema targetNamespace="urn:vgx-realtime" xmlns="http://www.w3.org/2000/10/XMLSchema";> - <complexType name="getRTQuote"> - <sequence> <element name="symbol" type="xsd:string" /> </sequence> </complexType> - <complexType name="getRTQuoteResponse"> - <sequence> - <element name="stock_quote"> - <complexType> - <sequence> <element name="symbol" type="xsd:string" /> <element name="time" type="xsd:string" /> <element name="last" type="xsd:string" /> <element name="change" type="xsd:string" /> <element name="pctchange" type="xsd:string" /> <element name="bid" type="xsd:string" /> <element name="ask" type="xsd:string" /> </sequence> </complexType> </element> </sequence> </complexType> </schema> </types>
