Hi Cory: WSDL please? :)
--G > -----Original Message----- > From: Cory Wilkerson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 13, 2003 4:28 PM > To: [EMAIL PROTECTED] > Subject: nightly drops generating bad responses? > > > I've noticed that in the latest nightly drops -- the response > coming out of axis is namespace qualifying some elements that > it doesn't namespace qualify in the 1.1 release. As a > result, .NET functionality is busted. My question is -- is > my service technically invalid and the fucntionality is fixed > in the nightly drops or are the nightly drops generating > incorrect responses. > > Can someone validate me or otherwise? > Thanks, > Cory > > Bad response (nightly drop): > -------------- > <ns1:requestResponse > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encodin > g/" xmlns:ns1="http://www.travelnow.com/services/HotelList";> > <ns1:requestReturn xsi:type="ns2:XmlResponse" > xmlns:ns2="http://common.xml.travelnow.com";> > <ns1:errorInfo xsi:type="ns2:ErrorInfo" xsi:nil="true"/> > <ns1:response xsi:type="ns3:HotelListResponse" > xmlns:ns3="http://list.hotel.xml.travelnow.com";> > > Good (meaning .net digests it nicely) response (1.1 release): > --------------- > <ns1:requestResponse > soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encodin > g/" xmlns:ns1="http://www.travelnow.com/services/HotelList";> > <requestReturn xsi:type="ns2:XmlResponse" > xmlns:ns2="http://common.xml.travelnow.com";> > <errorInfo xsi:type="ns2:ErrorInfo" xsi:nil="true"/> > <response xsi:type="ns3:HotelListResponse" > xmlns:ns3="http://list.hotel.xml.travelnow.com";> >
