RE: [jira] Commented: (AXIS-1605) SOAPFaultException should be th row instead of AxisFault to be compliant with JAX-RPC 1.1

[Tom Jordahl <to...@macromedia.com>]

I agree with Rick on this.

I don't see us changing the way we do exceptions via AxisFault any time
soon.

--
Tom Jordahl
Macromedia Server Development

> -----Original Message-----
> From: Kellogg, Richard [mailto:RKellogg@MICROS.COM]
> Sent: Wednesday, October 13, 2004 2:33 PM
> To: axis-dev@ws.apache.org
> Subject: RE: [jira] Commented: (AXIS-1605) SOAPFaultException should be
> throw instead of AxisFault to be compliant with JAX-RPC 1.1
> 
> -1 to any more special flags.  This type of behavior will just kill us
> long term when it comes to interop.
> 
> Just my two cents.
> Rick Kellogg
> 
> 
> -----Original Message-----
> From: axis-dev@ws.apache.org [mailto:axis-dev@ws.apache.org]
> Sent: Wednesday, October 13, 2004 2:30 PM
> To: axis-dev@ws.apache.org
> Subject: [jira] Commented: (AXIS-1605) SOAPFaultException should be
> throw instead of AxisFault to be compliant with JAX-RPC 1.1
> 
> 
> The following comment has been added to this issue:
> 
>      Author: Sébastien Tardif
>     Created: Wed, 13 Oct 2004 11:28 AM
>        Body:
> SOAPFaultException has those methods:
> - Detail getDetail()     // Gets the detail element.
> - String getFaultActor() // Gets the faultactor element.
> - QName	getFaultCode()   // Gets the faultcode element.
> - String getFaultString()// Gets the faultstring element.
> 
> Detail class derived from Node:
> Interface Detail
> All Superinterfaces:
> Node, SOAPElement, SOAPFaultElement
> 
> So it seems SOAPFaultException also permit to receive all the XML of the
> fault detail.
> 
> Let's agree JAX-RPC specification is suck because it allow Axis to be
> compliant without using the SOAPFaultException which is more standard and
> do the same thing as AxisFault.
> 
> Now do we want to improve Axis and support a flag which will change this
> behavior?
> ---------------------------------------------------------------------
> View this comment:
>   http://issues.apache.org/jira/browse/AXIS-
> 1605?page=comments#action_54009
> 
> ---------------------------------------------------------------------
> View the issue:
>   http://issues.apache.org/jira/browse/AXIS-1605
> 
> Here is an overview of the issue:
> ---------------------------------------------------------------------
>         Key: AXIS-1605
>     Summary: SOAPFaultException should be throw instead of AxisFault to be
> compliant with JAX-RPC 1.1
>        Type: Bug
> 
>      Status: Unassigned
>    Priority: Major
> 
>     Project: Axis
>    Versions:
>              1.2 Beta
> 
>    Assignee:
>    Reporter: Sébastien Tardif
> 
>     Created: Tue, 12 Oct 2004 9:35 AM
>     Updated: Wed, 13 Oct 2004 11:28 AM
> Environment: Axis 9/23/2004
> 
> Description:
> SOAPFaultException should be throw instead of AxisFault to be compliant
> with JAX-RPC 1.1.
> 
> Right now as a Axis client of a webservices implemented with Axis I
> receive an AxisFault instead of a SOAPFaultException.
> 
> The JAX-RPC 1.1 said:
> 
> From 4.3.6:
> A wsdl:fault is mapped to either a java.rmi.RemoteException (or its
> subclass),
> service specific Java exception (described later in this section) or a
> javax.xml.rpc.
> soap.SOAPFaultException. Refer to the section 6.5, "SOAP Fault" for more
> details on
> the Java mapping of a WSDL fault based on the SOAP binding.
> Refer to the section 14.3.6, "Mapping of Remote Exceptions" for the
> mapping between
> the standard SOAP faults [5] and the java.rmi.RemoteException.
> ...
> Service Specific Exception
> A service specific Java exception (mapped from a wsdl:fault and the
> corresponding
> wsdl:message) extends the class java.lang.Exception directly or
> indirectly.
> The single message part in the wsdl:message (referenced from the
> wsdl:fault
> element) may be either a type or an element. If the former, it can be
> either a
> xsd:complexType or a simple XML type.
> Each element inside the xsd:complexType is mapped to a getter method and a
> parameter in the constructor of the Java exception. Mapping of these
> elements follows
> the standard XML to Java type mapping. The name of the Java exception
> class is
> mapped from the name attribute of the xsd:complexType for the single
> message part.
> This naming scheme enables the WSDL to Java mapping to map an
> xsd:complexType
> derivation hierarchy to the corresponding Java exception class hierarchy.
> The following
> section illustrates an example. Refer to the section
> 
> From 6.5:
> A SOAP fault is mapped to either a javax.xml.rpc.soap.SOAPFaultException,
> a
> service specific exception class or RemoteException.
> 
> - Without this bug I could change of webservices runtime compliant with
> JAX-RPC and keep the same Java code.
> - AxisFault is not a service specific Exception and so should not derived
> from RemoteException.
> 
> 
> ---------------------------------------------------------------------
> JIRA INFORMATION:
> 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
> 
> If you want more information on JIRA, or have a bug to report see:
>    http://www.atlassian.com/software/jira