Hi Dan,
The first part of your reply was pretty straightforward. I created my own
version of OutgoingChainInterceptor and at the end of handleMessage
I did:
message.getInterceptorChain().pause();
This stops the current chain, right? Now I still created my new response,
put that inside the message content.
Now comes the bit I don't quite understand how to do. I put the interceptor
in the SETUP phase, was that correct?
Also, how to pause the fault chain is unclear to me. The current chain IS
the fault chain, isn't it?
What happens now when I invoke my call is, that my custom
OutgoingChainInterceptor is reached but it ends there. I tried resuming the
chain but that just shows the 'response object is null' exception which
seems kind of logical since this is the same chain as I understand :-)
Maybe you could provide me with an example on how to make this interceptor
change from fault chain to normal chain and handle the reponse as normal
response?
Thanx so far!
Ronald
dkulp wrote:
>
>
> What you may want to try is take the code for the OutgoingChainInterceptor
> from:
>
> http://svn.apache.org/repos/asf/cxf/trunk/rt/core/src/main/java/org/apache/cxf/interceptor/OutgoingChainInterceptor.java
>
> And pretty much duplicate it. the only addition would be to, at the very
> end, grab the current chain and pause it. Stick it as the FIRST
> interceptor
> on the Fault chain. That should work fine as you would be setting up an
> outgoing chain exactly like the normal responses. Don't forget to
> stop/pause
> the fault chain so it then doesn't try sending a fault as well. ;-)
>
> Dan
>
--
View this message in context:
http://old.nabble.com/Response-object-is-null-tp28859579p28867215.html
Sent from the cxf-user mailing list archive at Nabble.com.
