Return-Path: 
 <axis-user-return-17602-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 15439 invoked by uid 500); 13 Aug 2003 20:35:51 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
list-post: <mailto:axis-user@xml.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 15424 invoked from network); 13 Aug 2003 20:35:50 -0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: nightly drops generating bad responses?
Date: Wed, 13 Aug 2003 15:35:56 -0500
Message-ID: <2F9013BBE7AA2D41925865227016ACC742F6E0@exchange.webify.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: nightly drops generating bad responses?
Thread-Index: AcNh2VlYN5d1KlvoQBCM27zSTdu43AAALCCw
From: "Mike Perham" <Mike.Perham@webifyinc.com>
To: <axis-user@ws.apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

I patched this in my own copy since it is also invalid according to
BP1.0.  Note that I just discovered this earlier today so let me know
how well it works for you.  Axis' test suite does pass with this patch.
I have not submitted an official patch to axis-dev yet.


Index: RPCProvider.java
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file:
/home/cvspublic/xml-axis/java/src/org/apache/axis/providers/java/RPCProv
ider.java,v
retrieving revision 1.107
diff -r1.107 RPCProvider.java
345,346c345
<                     returnQName =3D new QName(body.getNamespaceURI(),
<                     methodName + "Return");
---
>                     returnQName =3D new QName(methodName + "Return");


-----Original Message-----
From: Cory Wilkerson [mailto:cwilkerson@travelnow.com]=20
Sent: Wednesday, August 13, 2003 3:28 PM
To: axis-user@xml.apache.org
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. =20

Can someone validate me or otherwise?
Thanks,
Cory

Bad response (nightly drop):
--------------
<ns1:requestResponse
soapenv:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1=3D"http://www.travelnow.com/services/HotelList">
      <ns1:requestReturn xsi:type=3D"ns2:XmlResponse"
xmlns:ns2=3D"http://common.xml.travelnow.com">
        <ns1:errorInfo xsi:type=3D"ns2:ErrorInfo" xsi:nil=3D"true"/>
        <ns1:response xsi:type=3D"ns3:HotelListResponse"
xmlns:ns3=3D"http://list.hotel.xml.travelnow.com">

Good (meaning .net digests it nicely) response (1.1 release):
---------------
<ns1:requestResponse
soapenv:encodingStyle=3D"http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1=3D"http://www.travelnow.com/services/HotelList">
     <requestReturn xsi:type=3D"ns2:XmlResponse"
xmlns:ns2=3D"http://common.xml.travelnow.com">
       <errorInfo xsi:type=3D"ns2:ErrorInfo" xsi:nil=3D"true"/>
       <response xsi:type=3D"ns3:HotelListResponse"
xmlns:ns3=3D"http://list.hotel.xml.travelnow.com">