Basically I want to rollback the changes made to the database if any problems occur sending data back to the client. I want to trap anything that will keep the client from receiving the return message so that I can rollback and keep the two in sync.

 

Brian Davis

Software Developer

JMM Ventures


From: Sunil Kothari [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 05, 2005 12:03 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [SPAM] Re: Running code outside of actual SOAP transaction?

 

Hi Brian,

    I think you need to be specific about what kind of exceptions you would like to trap. Is it runtime exceptions or remote exceptions or soapexceptions or your application exceptions.

 

In case its the exceptions thrown by your application then you need to mention them in your WSDL.

 

I found this article very useful

 but I must remind you that java2wsdl doesn't do a neat job in handling exception hierarchy.

 

I hope that helps.

Sunil Kothari

----- Original Message -----

From: Brian Davis

Sent: Wednesday, January 05, 2005 4:08 AM

Subject: Running code outside of actual SOAP transaction?

 

I am using Java2WSDL and WSDL2Java to create a service from a simple Java interface. I would like to trap any exceptions/faults that occur during the SOAP exchanges and then execute some code depending on whether there are any faults or not. I’m not sure where I need to put this code, none of the generated classes seem appropriate.

 

Thanks a ton!

 

Brian Davis

Software Developer

JMM Ventures

 

Reply via email to