axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 24845] - complexType in SOAP response has namespace prefix, chokes .net clients
Date Mon, 05 Jan 2004 18:28:21 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24845>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24845

complexType in SOAP response has namespace prefix, chokes .net clients

gdaniels@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From gdaniels@apache.org  2004-01-05 18:28 -------
Hi folks:

This works fine for me.  When I deploy as follows:

 <service name="Test" style="rpc" xmlns:ns="http://myns">
  <parameter name="allowedMethods" value="*"/>
  <parameter name="className" value="SimpleService"/>
  <beanMapping type="java:MyCustomType" qname="ns:t1"/>
  <beanMapping type="java:BobType" qname="ns:t2"/>
 </service>

I get this response from op2:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
  <op2Response 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
   <op2Return href="#id0"/>
  </op2Response>
  <multiRef id="id0" soapenc:root="0" 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
xsi:type="ns1:t1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" 
xmlns:ns1="http://myns">
   <bar xsi:type="soapenc:string">fooEl1</bar>
   <bar xsi:type="soapenc:string">fooEl2</bar>
   <bar xsi:type="soapenc:string">fooEl3</bar>
   <bob href="#id1"/>
   <foo xsi:type="soapenc:string">foo value</foo>
   <lotsOfBob href="#id2"/>
   <lotsOfBob href="#id3"/>
  </multiRef>
  <multiRef id="id3" soapenc:root="0" 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
xsi:type="ns2:t2" xmlns:ns2="http://myns" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
   <AString xsi:type="soapenc:string">bobEl2</AString>
  </multiRef>
  <multiRef id="id1" soapenc:root="0" 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
xsi:type="ns3:t2" xmlns:ns3="http://myns" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
   <AString xsi:type="soapenc:string">bob value</AString>
  </multiRef>
  <multiRef id="id2" soapenc:root="0" 
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
xsi:type="ns4:t2" xmlns:ns4="http://myns" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
   <AString xsi:type="soapenc:string">bobEl1</AString>
  </multiRef>
 </soapenv:Body>
</soapenv:Envelope>

I'm using the CVS as of today - if this doesn't work for you with 1.2alpha, 
please try the latest CVS (this got fixed with my big batch of type mapping 
changes).  I'm going to mark this "FIXED" for now, and if you continue to have 
problems with the CVS version, please reopen.

Mime
View raw message