Just as you have servlet filters to filter, you can filter web services using soap handlers. (You could 'catch' the outgoing exception in a response handler, log it, and then let it go onto the client). -jeff
-----Original Message----- From: Ham MI-AJ, Oliver Misch [mailto:[EMAIL PROTECTED] Sent: Friday, July 13, 2007 6:30 AM To: [email protected] Subject: Centralized handling of RuntimeExceptions Hi, Is there a way to handle RuntimeExceptions that are raised during the execution of web services in a centralized way on the server side? When our services propagate RuntimeExceptions, we would like to catch them - may be in a special exception handler - log them and raise an AxisFault with a certain code and description. I know that RuntimeExceptions are caught somewhere in Axis2 and are wrapped by a standard AxisFault. But we would like to specify our one codes and do te logging. E.g. when using servlets, I would implement a special servlet filter that acts as a central exception handler. Thanx in advance and best regards, Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
