minor non-conformance of exceptions to JSR-181 / JAX-RPC 1.1
------------------------------------------------------------

         Key: BEEHIVE-717
         URL: http://issues.apache.org/jira/browse/BEEHIVE-717
     Project: Beehive
        Type: Bug
  Components: Web Services (181)  
    Versions: V1Beta    
 Environment: Beehive SVN 169852
    Reporter: Jeremiah Johnson
 Assigned to: daryoush mehrtash 
    Priority: Minor
     Fix For: V1


While testing BEEHIVE-133, we ran into an issue with user-defined Exceptions.  
The example provided in the JAX-RPC v1.1 spec shows the problem, so I will 
attach that as the repro.  The WSDL looks accurate according to the JAX-RPC 
spec (which is referenced by JSR 181), but the response message looks incorrect.

I will attach the WSDL; the incorrect looking response is below:

<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>
  <soapenv:Fault>
   <faultcode>soapenv:Server.userException</faultcode>
   <faultstring>web.InvalidTickerException</faultstring>
   <detail>
    <ns1:hostname 
xmlns:ns1="http://xml.apache.org/axis/";>localhost.localdomain</ns1:hostname>
   </detail>

  </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to