beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "daryoush mehrtash (JIRA)" <>
Subject [jira] Commented: (BEEHIVE-717) minor non-conformance of exceptions to JSR-181 / JAX-RPC 1.1
Date Tue, 07 Jun 2005 01:01:42 GMT
    [ ] 

daryoush mehrtash commented on BEEHIVE-717:

There are two problems with Faults.   

If the JWS is called from the URL, Axis would not serialize the fault properly and you get
a bogus message.  I have send a patch for axis to fix this problem.

The other issue is when you send a soap request (e.g. via application) to the JWS, JWS was
not sending the correct infomration in the detail.    I fixed the JWS based on this exchange.  

The fixes are attached shortly.

> minor non-conformance of exceptions to JSR-181 / JAX-RPC 1.1
> ------------------------------------------------------------
>          Key: BEEHIVE-717
>          URL:
>      Project: Beehive
>         Type: Bug
>   Components: Web Services (181)
>     Versions: V1Beta
>  Environment: Beehive SVN 169852
>     Reporter: Jeremiah Johnson
>     Assignee: daryoush mehrtash
>     Priority: Minor
>      Fix For: TBD
>  Attachments: BEEHIVE-133.tar.gz, BEEHIVE-133.wsdl, faultpatch.txt
> 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="" xmlns:xsd=""
>  <soapenv:Body>
>   <soapenv:Fault>
>    <faultcode>soapenv:Server.userException</faultcode>
>    <faultstring>web.InvalidTickerException</faultstring>
>    <detail>
>     <ns1:hostname xmlns:ns1="">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:
For more information on JIRA, see:

View raw message