Okay. So I fiddled with the onFault a little more and I think I found a solution.  Since the java provider is implemented as a handler, I guess I can use the onFault for the handlers declared in the request flow to do exception handling processing.  I guess I was hoping there'd be a separate fault chain declaration to clearly delineate between request flow logic and exception handling logic.  But this will suffice.

 

Wei

 

-----Original Message-----
From: Wei Hsu [mailto:[EMAIL PROTECTED]
Sent: Friday, August 20, 2004 12:37 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Adding SOAP header to SOAP Faults

 

Do you mean that there exists a fault response chain mechanism in Axis, or that Axis needs to develop such fault response chain? If such mechanism does exist, do you mind pointing me to it?  I've been looking for it for a while now. Thanks!

 

Wei

 

-----Original Message-----
From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
Sent: Friday, August 20, 2004 11:50 AM
To: [EMAIL PROTECTED]
Subject: RE: Adding SOAP header to SOAP Faults

 

Sounds like we need a fault response chain.

 


From: Wei Hsu [mailto:[EMAIL PROTECTED]
Sent: Friday, August 20, 2004 1:47 PM
To: [EMAIL PROTECTED]
Subject: Adding SOAP header to SOAP Faults

 

Hi all,

 

I'm trying to add a customized SOAP Header to all responses returned from the server to the client.  So far I'm doing this with a handler registered in the response flow.  This works fine for normal responses, but not for SOAP faults.  Please correct me if I'm wrong, but I don't' think the response chain is invoked on a fault.  If that is the case, other than adding that header during serialization with my own custom fault serializers, are there any other ways to go about this?   Would really appreciate any help.  Thanks!

 

Wei

Reply via email to