beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie O'Neil (JIRA)" <beehive-...@incubator.apache.org>
Subject [jira] Commented: (BEEHIVE-717) minor non-conformance of exceptions to JSR-181 / JAX-RPC 1.1
Date Tue, 07 Jun 2005 21:26:44 GMT
    [ http://issues.apache.org/jira/browse/BEEHIVE-717?page=comments#action_12312940 ] 

Eddie O'Neil commented on BEEHIVE-717:
--------------------------------------

Daryoush--

Gotcha -- one question I have is about whether the ControlProvider would ever throw an AxisFault
and if it did why we would ever need to catch it.  The bridge between WSM and Axis seems to
be tied up in AxisHook.createServiceDesc(...), so it seemed weird to catch AxisFault in ControlProvider
when that's just used to initialize @Control references.  

If the goal is to catch application exceptions, can we just re-throw all AxisFault(s) and
wrap the rest?  Might simplify the catch logic.

The other changes sound great.   I'll watch for a new patch.

> 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
>     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="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


Mime
View raw message