Are you using Axis1 or Axis2? If you are using Axis1, then you'll need to catch the HTTP 500 error code. Your client won't actually receive the SOAP fault, because Axis won't process any returned SOAP messages.
If you're using Axis 2, along with SOAP 1.2 and WSDL 2.0, then you can use the Robust In-Only MEP [1], which supports return of fault messages. [1] http://www.w3.org/TR/2005/WD-wsdl20-adjuncts-20050803/#patterns Anne On 8/17/05, Gordon Gekko <[EMAIL PROTECTED]> wrote: > Hi! > > I've a question about in-only message exchange pattern and exception. > > I've written a client and a server that both manage in-only message > exchange. Now, when the server computation goes fine I get back a http > packet with 202 (accepted) as response code and when something goes > wrong an exception is raised in the server and I get back an http > message with response code 500 (internal server error) and a soap fault > message in the body. But in the latter case an exception is not raised > in the client so I cannot notice that something went wrong in the server. > > I know that it is called "fire and forget" but I should not be aware > that something went wrong in the server? Or am I doing something wrong? > > Thanks a lot for any reply! > > Diego > >
