ansaurus

Question

Spring Web Services - Exception Skipping ExceptionResolver

Answer 1

A:

You have to "wire" (or "inject") the exception handler in your spring beans. I'm not sure which of your Spring bean actually needs the exception handler.

Personally, I use default-autowire="byName", which cause my exceptionHandler to be wired in my Controller class automatically. Your approach actually use manual wiring. So you need to find out which bean should actually use the exception handler. Have you tried (just on top of my head):

<bean class="org.springframework.ws.server.endpoint.adapter.MarshallingMethodEndpointAdapter">
    <constructor-arg ref="marshaller"/>
    <property name="exceptionHandler" ref="exceptionHandler" />
</bean>

Or you could just add the autowired mechanism of Spring and let it wire the beans automatically. :)

Thierry-Dimitri Roy 2010-08-18 15:07:06

the exception resolver I defined is automatically used during the lifecycle of the SOAP call, however the exception that I gave the trace of is for some reason not handled by it. Either it's because the resolver doesn't handle exceptions yet in the life-cycle, or this exception is somehow slipping through uncaught.

walnutmon 2010-08-20 04:02:15

I say this because the MarshallingMethodEndpointAdapter doesn't have a property "exceptionHandler", so you could not inject one in this fashion, unless I'm missing something

walnutmon 2010-08-20 04:03:07

Answer 2

+1 A:

I remember running into this kind of problem when working with spring-security. I also had issues with my exception resolver not being invoked under some condititions.

The problem then was that there is a filter chain that handles each request. The code that invokes the exception resolvers is a filter in this chain, but it is close to the end of the chain. Hence, if an exception ocurred somewhere within the filters before the exception resolver invoking filter, my resolver would never be invoked.

I am guessing you suffer from something similar here, where envelope parse errors happen before the exception resolver invoking filter. If that is the case, you will have to resort to some other way of handling those exceptions, for example a vanilla servlet filter.

Kristoffer E 2010-08-20 12:00:18

Answer 3

+1 A:

I've looked more closely at your question and I think that I know what's happening. You exception handler is not called because it is in the higher level in the soap processing. You see, WebServiceMessageReceiverHandlerAdapter tries to decode the incoming string to an XML before sending it to the marshaller to be processed. Since the XML is invalid the call fails. And since WebServiceMessageReceiverHandlerAdapter does not support an exception handler, it just rethrows the exception "SaajSoapMessageException".

Now what you can do is create a new class that extends WebServiceMessageReceiverHandlerAdapter, but that also wraps handleConnection() in a try/catch that uses your exception handler when a exception is throw.

By the way, when debugging this kind of problem my approach is to output both method name and line number in log4j. As well as downloading the Spring sources.

Thierry-Dimitri Roy 2010-08-20 12:18:10

I could subclass, but how would I tell spring to use that implementation? I don't see any place where that is configurable

walnutmon 2010-08-23 16:33:44

I want to add you're completely correct, however I don't have any solution to actually fixing this problem, I'm not sure how to leverage my implementation of the WebServiceMessageReceiverHandlerAdapter in my web service project, the way I understand it only certain beans are automatically picked up within the servlet-context.xml. At some point this week I will try just definining this sub-classed bean in the context file and see if it is used automagically, if you think you know how to override let me know, and the bounty is yours

walnutmon 2010-08-25 13:05:35

ansaurus

tags:

views:

answers:

Spring Web Services - Exception Skipping ExceptionResolver

related questions