Hi Pedro, I know that everything is easier with AxisFault, but I have to construct some JAX-RPC handlers (instead of Axis handler) that need to work in every JAX-RPC SOAP engine. Axis is one of this, but there are some points where Axis doesn't fulfil the JAX-RPC standard. The SOAPFaultException is in the JAX-RPC standard but it doesn't work in Axis. Regards, Jorge
-----Mensaje original----- De: Pedro Salazar [mailto:[EMAIL PROTECTED] Enviado el: martes, 18 de noviembre de 2003 18:20 Para: [EMAIL PROTECTED] Asunto: RE: SOAPFaultException in Axis On Mon, 2003-11-10 at 17:54, Jorge Lorenzo wrote: > When you create a SOAPFaultException, you specify four elements (in the > constructor): > SOAPFaultException(QName faultcode, String faultstring, String faultactor, > Detail faultdetail) > But Axis only uses the faultstring (and in part because it's appended to the > exception classname). The rest of parameters, included the faultcode, are > ommitted by Axis. So I don't think it's very useful the implementation of > SOAPFaultException. In fact, it's easier to use the JAXRPCException which > just requires a string parameter. > You should use AxisFaults instead the SOAPFaultExceptions because Axis is intended to process onFault() methods of all handlers already processed in the chain in case of fault. And this would only happen if an AxisFault was thrown, and not a SOAPFaultException. Unless you don't need the handlers onFault() methods behavior, of course. -- -PS
