Benson, The areas that I usually have breakpoints set when doing low level debugging are:
PhaseInterceptorChain: I ALWAYS have a breakpoint in the "catch" clause as line 210. If anything throws an exception, it usually ends up there. When trying to figure out whats going on, I have a breakpoint on the line just above that: currentInterceptor.handleMessage(message); so I can trace into any interceptor that seems "interesting". When doing Databinding work, you also need a breakpoint in the AbstractOutDatabindingInterceptor and AbstractInDatabindingInterceptor. Specifically, if you break in the getDataReader/getDataWriter calls, you can trap where it is preparing to write the objects. Dan On Wednesday 19 September 2007, Benson Margulies wrote: > If you wade through this log, you will see a message arriving at the > client that has all the elements of a map. Yet, an empty map is > returned to the client. > > I'm having the devil's time even figuring out what breakpoint to set > to make any sense of this state of affairs. The 'resList' (the > List.class item on the input message) stays empty. I don't know who is > supposed to set it. I'd sort-of guess 'the > DocumentLiteralInterceptor', but I don't know. > > Can anyone give me a leg up here? > -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
