Return-Path: 
 <users-return-37586-apmail-cxf-users-archive=cxf.apache.org@cxf.apache.org>
X-Original-To: apmail-cxf-users-archive@www.apache.org
Delivered-To: apmail-cxf-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 7B453D579
	for <apmail-cxf-users-archive@www.apache.org>;
 Fri, 30 Nov 2012 16:01:09 +0000 (UTC)
Received: (qmail 14129 invoked by uid 500); 30 Nov 2012 16:01:08 -0000
Delivered-To: apmail-cxf-users-archive@cxf.apache.org
Received: (qmail 13913 invoked by uid 500); 30 Nov 2012 16:01:08 -0000
Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@cxf.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@cxf.apache.org>
List-Post: <mailto:users@cxf.apache.org>
List-Id: <users.cxf.apache.org>
Reply-To: users@cxf.apache.org
Delivered-To: mailing list users@cxf.apache.org
Received: (qmail 13154 invoked by uid 99); 30 Nov 2012 16:01:06 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Nov 2012 16:01:06 +0000
X-ASF-Spam-Status: No, hits=2.0 required=5.0
	tests=SPF_NEUTRAL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of johnbright.j@gmail.com)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Nov 2012 16:01:00 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <johnbright.j@gmail.com>)
	id 1TeT15-0003XP-Ek
	for users@cxf.apache.org; Fri, 30 Nov 2012 08:00:39 -0800
Date: Fri, 30 Nov 2012 08:00:39 -0800 (PST)
From: jbright <johnbright.j@gmail.com>
To: users@cxf.apache.org
Message-ID: <38F7A513-78B6-4F56-A540-6AC2C3D62CE2@gmail.com>
In-Reply-To: <D225CD69196F3F4A9F4174B2FCA06F886BFB3D@S10BE002.SH10.lan>
References: <1354268997349-5719484.post@n5.nabble.com>
 <D225CD69196F3F4A9F4174B2FCA06F886BFB3D@S10BE002.SH10.lan>
Subject: Re: Response not coming in SOAPUI
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

It worked as I found the message was not set correct in the code.

Yes we do throw exception and a custom error message is created.

I extended AbstractSoapInterceptor as our requirement is to authenticate using LDAP.



Thanks
John

On Nov 30, 2012, at 7:14 PM, "Andrei Shakirin [via CXF]" <ml-node+s547215n5719497h71@n5.nabble.com> wrote:

> 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:[hidden email]] 
> > Sent: Freitag, 30. November 2012 10:50 
> > To: [hidden email] 
> > 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. 
> 
> 
> If you reply to this email, your message will be added to the discussion below:
> http://cxf.547215.n5.nabble.com/Response-not-coming-in-SOAPUI-tp5719484p5719497.html
> To unsubscribe from Response not coming in SOAPUI, click here.
> NAML




--
View this message in context: http://cxf.547215.n5.nabble.com/Response-not-coming-in-SOAPUI-tp5719484p5719511.html
Sent from the cxf-user mailing list archive at Nabble.com.