Nils-Helge, Please try a nightly build, if you still see the problem, open up a bug report.
thanks, dims On Fri, 04 Jun 2004 14:41:43 +0100, Nils-Helge Garli <[EMAIL PROTECTED]> wrote: > > The correct WSDL should be: > > <definitions targetNamespace="http://www.myns.com/ws";> > <types> > <s:schema elementFormDefault="qualified" > targetNamespace="http://www.myns.com/ws";> > > > > ----- Original Message ----- > From: "Nils-Helge Garli" <[EMAIL PROTECTED]> > Date: Fri, 04 Jun 2004 14:34:26 +0100 > To: [EMAIL PROTECTED] > Subject: RE: Dynamic client/WSDL problems > > > Thanks for the quick answer. > > > > The top of the WSDL document looks like this: > > > > <definitions targetNamespace="http://www.myns.com/ws";> > > <types> > > <s:schema elementFormDefault="qualified" > > targetNamespace="http://www.superoffice.net/ws";> > > > > The WSDL file has been automatically generated by .NET, and since I'm not the > > "owner" of the WSDL file, I can't modify it easily. > > > > Sincererly, > > > > Nils-Helge Garli > > > > > > ----- Original Message ----- > > From: "Anne Thomas Manes" <[EMAIL PROTECTED]> > > Date: Fri, 4 Jun 2004 09:05:51 -0400 > > To: <[EMAIL PROTECTED]> > > Subject: RE: Dynamic client/WSDL problems > > > > > One question: what is the value of the elementFormDefault attribute? > > > > > > If it's "qualified", then you are correct that the proper QName for the > > > element is {http://www.myns.com}departmentId. But if it's "unqualified" (or > > > not specified), then the element is a local element, and it has no QName -- > > > only a local name, and it requires its parent element for context. > > > > > > Certainly generation of an element name of > > > ">GetDepartmentPhoneList>departmentId" is a bug, but I suspect it only > > > occurs when using unqualified names. > > > > > > (I noticed that Suteertha had this problem too.) > > > > > > On the flip side, if wsdl2java generates a QName for a local element, that's > > > also a bug. > > > > > > Please file a bug report. > > > > > > Anne > > > > > > -----Original Message----- > > > From: Nils-Helge Garli [mailto:[EMAIL PROTECTED] > > > Sent: Friday, June 04, 2004 7:55 AM > > > To: [EMAIL PROTECTED] > > > Subject: Dynamic client/WSDL problems > > > > > > Hi! > > > > > > I have a problem trying to access a .NET web service with the Axis (1.2 > > > beta) dynamic proxy client. The QNames of the WSDL are parsed incorrectly. > > > For instance, parsing this part (from the WSDL file): > > > > > > <s:element name="GetDepartmentPhoneList"> > > > <s:complexType> > > > <s:sequence> > > > <s:element minOccurs="1" maxOccurs="1" name="departmentId" > > > type="s:int"/> > > > </s:sequence> > > > </s:complexType> > > > </s:element> > > > > > > results in a qname like: > > > > > > {http://www.myns.com}>GetDepartmentPhoneList>departmentId, and when this is > > > serialized in the call, the resulting xml is > > > > > > <>GetDepartmentPhoneList>departmentId>1</>GetDepartmentPhoneList>departmentI > > > d> > > > > > > which of course results in a "bad request" from the service. So the local > > > part of QName is in fact interpreted as > > > '>GetDepartmentPhoneList>departmentId' which is wrong. Using WSDL2Java and > > > generating the classes, I see that the generated stub uses the QName > > > {http://www.myns.com}departmentId, which is correct. > > > > > > How come the generated classes and the dynamic proxy generated WSDL are > > > different? Are there some options/settings I can use to prevent this from > > > happening? > > > > > > Thank you. > > > > > > Sincererly, > > > > > > Nils-Helge Garli > > > -- > > > _____________________________________________________________ > > > Web-based SMS services available at http://www.operamail.com. > > > >From your mailbox to local or overseas cell phones. > > > > > > Powered by Outblaze > > > > > > > -- > > _____________________________________________________________ > > Web-based SMS services available at http://www.operamail.com. > > From your mailbox to local or overseas cell phones. > > > > Powered by Outblaze > > -- > _____________________________________________________________ > Web-based SMS services available at http://www.operamail.com. > From your mailbox to local or overseas cell phones. > > Powered by Outblaze >
