Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (nike.apache.org: domain of asoldano@redhat.com designates
 209.132.183.28 as permitted sender)
Message-ID: <5244561D.9040601@redhat.com>
Date: Thu, 26 Sep 2013 17:43:25 +0200
From: Alessio Soldano <asoldano@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: dev@cxf.apache.org
Subject: Custom HandlerChainInvoker
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,
I currently have an integration requirement which basically imply having 
to perform some additional authorization checks just before invoking any 
JAXWS handler handleMessage method.

For achieving that, I've thought about using a custom 
HandlerChainInvoker overriding 'invokeLogicalHandlers' and 
'invokeProtocolHandlers' methods.
For installing such a custom invoker, I thought about adding a custom 
AbstractPhaseInterceptor running just before the SOAPHandlerInterceptor 
in the PRE_PROTOCOL_FRONTEND phase; the new handler would install my 
invoker in the Exchange, similarly to what is done in 
AbstractJAXWSHandlerInterceptor#getInvoker.
The problem I have, however, is that ofcourse I need a handle to the 
handler chain (List<Handler>) to build the invoker: the handler chain is 
available from the Endpoint stored in the current exchange, if the 
endpoint is an instance of JaxWsEndpointImpl. Any idea / hint on how to 
get that there easily for other Endpoint types?
Does the whole flow here make sense?
Would it make sense to allow a more direct customization of the handler 
chain invoker?

Thanks
Alessio

-- 
Alessio Soldano
Web Service Lead, JBoss