wood burning stoves 2.0*
The moose likes Web Services and the fly likes unexpected result when throwing SOAPFaultException Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "unexpected result when throwing SOAPFaultException " Watch "unexpected result when throwing SOAPFaultException " New topic
Author

unexpected result when throwing SOAPFaultException

michael warren
Ranch Hand

Joined: Oct 20, 2006
Posts: 50
Hi,

I find that when I throw a SOAPFaultException from a handler's handleRequest method the request is returned to the client as is, whereas I was expecting the SOAPFaultException to be used to automatically generate a fault repsonse.

If I throw a runtime exception then a fault repsonse is returned.

I've had a search for this and looked at sites like
IBM's Exception Handling with JAX-RPC , but still am none the wiser as to whether what I'm expecting is wrong.

Any ideas ?



I'm using Sun's Application Server 8.2 i.e. SAAJ 1.2 and I think JAX-RPC 1.1
michael warren
Ranch Hand

Joined: Oct 20, 2006
Posts: 50
Just to update, I have found this :
https://jax-rpc.dev.java.net/servlets/ReadMsg?listName=users&msgNo=1522

It
is then the responsibility of the current handler (or other handlers in
the chain) to create the SOAP fault


Which suggests that what I assumed was wrong and that when throwing SOAPFaultException from a handler your code also needs to change the body of the response to be a fault, which seems a bit convoluted - whats the point of populating the SOAPFaultException ?
I'm not using latest version of JAX-RPC (or JAX-WS which I think replaces it) as I'm studying for SCDJWS, so perhaps this isn't an issue anymore.
 
Don't get me started about those stupid light bulbs.
 
subject: unexpected result when throwing SOAPFaultException
 
Similar Threads
WSWS3192E: Error: return code: ( 400 ) Bad Request when trying to invoked webservice
Getting the Raw Request and Response XML from axis.
Problem in Attachments
Attachment problem
Sign soap header with handler in WebSphere 6.1