I think more appropriate solution will be throwing the exception instead aborting interceptor chain in case of failed authentication. It can be SoapFault exception (like in WSS4JInIntercepor), you will be able to set fault code, message and details as you want.
I am not sure why your solution doesn't work, seems that chain is aborted and response is hasn't been put in the message. May I ask what is the reason of introducing own authentication interceptor and not using CXF ones? CXF supports a lot of authentication schemas out of the box: HTTP basic, UsernameToken, SAML, Kerberos, etc. Cheers, Andrei. > -----Original Message----- > From: jbright [mailto:[email protected]] > Sent: Freitag, 30. November 2012 10:50 > To: [email protected] > Subject: Response not coming in SOAPUI > > I've introduced interceptor to read the request SoapMessage and do > authentication. > > If unauthenticated, I do abort() the interceptor chain and sending an error > message in the response. > > The problem is the response message is built using the SOAPMessage of > SAAJ. > ... > > When I make the request from the SOAPUI, the response is not coming back > in SOAPUI. > > But when I check the log, the response is there in the payload. > > I've used the SAAJOutInterceptor in the config file... > > <jaxws:outInterceptors> > <ref bean="saajOutInterceptor" /> > <ref bean="logOutbound" /> > </jaxws:outInterceptors> > > If I remove the SAAJOutInterceptor from the config file, the response is not > at all coming... > > > > -- > View this message in context: http://cxf.547215.n5.nabble.com/Response- > not-coming-in-SOAPUI-tp5719484.html > Sent from the cxf-user mailing list archive at Nabble.com.
