Resolved the issue, but think this is a bug in CXF framework. when Adding interceptor org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor$CheckClosingTagsInterceptor@37ae37ae to phase post-logical [2/28/12 14:15:57:731 EST] 0000005f PhaseIntercep 1 Chain org.apache.cxf.phase.PhaseInterceptorChain@79527952 was modified. Current flow: receive [PolicyInInterceptor, LoggingInInterceptor, AttachmentInInterceptor] pre-stream [CertConstraintsInterceptor, HttpsTokenInInterceptor] post-stream [StaxInInterceptor] read [WSDLGetInterceptor, SAAJPreInInterceptor, ReadHeadersInterceptor, SoapActionInInterceptor, StartBodyInterceptor] pre-protocol [MEXInInterceptor, MustUnderstandInterceptor, PolicyBasedWSS4JInInterceptor, UsernameTokenInterceptor] post-protocol [CheckFaultInterceptor, JAXBAttachmentSchemaValidationHack] unmarshal [URIMappingInterceptor, DocLiteralInInterceptor, SoapHeaderInterceptor] pre-logical [OneWayProcessorInterceptor] post-logical [WrapperClassInInterceptor, CheckClosingTagsInterceptor] pre-invoke [SwAInInterceptor, HolderInInterceptor, AccountValidator, *PolicyVerificationInInterceptor*] invoke [ServiceInvokerInterceptor] post-invoke [OutgoingChainInterceptor]
is adding PolicyVerificationInterceptor dynamically to the end of the list (after my application coded interceptor). Even if I say, my interceptor should be added after PolicyVerificationIn.., it does not help.; ReadHeadersInterceptor dynamically introduces PolicyVeirificationIn..as the last item and therefore gets into my application. What I am doing now is to add my custom interceptor under "invoke" phase before ServiceInvokerInterceptor. -- View this message in context: http://cxf.547215.n5.nabble.com/Multiple-endpoints-and-security-policy-tp5519904p5522968.html Sent from the cxf-user mailing list archive at Nabble.com.
