axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <dava...@gmail.com>
Subject Re: SOAPMessage vs. SOAPException in SOAPConnectionImpl
Date Sat, 25 Jun 2005 02:20:44 GMT
try 

"return new Message(af);" instead of "throw new SOAPException(af);"
and see if that helps.

-- dims

On 6/24/05, David Blevins <david.blevins@visi.com> wrote:
> Hey all,
> 
> Dealing with a very interesting failure.   It seems that anytime you use a SOAPConnection
to make a call, you only get a fault back if the the server sent it.  Anything that would
be a valid fault as per the WSI basic profile is rewrapped as a SOAPException and the fault
codes are lost.
> 
> SOAPConnectionImpl.java
> -----------------------------
>     public SOAPMessage call(SOAPMessage request, Object endpoint) throws SOAPException
{
>         ...
>         try {
>             Call call = new Call(endpoint.toString());
>             ...
>             call.invoke((Message) request);
>             return call.getResponseMessage();
>         } catch (java.net.MalformedURLException mue){
>             throw new SOAPException(mue);
>         } catch (org.apache.axis.AxisFault af){
>             throw new SOAPException(af);
>         }
>     }
> -----------------------------
> 
> Shouldn't this code create a SOAPMessage containing the fault rather than rewrap and
throw it as a SOAPException?
> 
> Thanks,
> David
> 


-- 
Davanum Srinivas -http://blogs.cocoondev.org/dims/

Mime
View raw message