Classification: UNCLASSIFIED Caveats: NONE Sorry, I meant the second issue, issue number 2, regarding the policy interceptor being called twice. Here's the original post about the second issue.
2. On the service side, my policy interceptor was called twice, once by RuntimeInvoker.invokeBinding() and once by DataTransformationInterceptor.invoke(). The latter baffled me because my policy.getPhase() returns service.binding.policy. Gang > -----Original Message----- > From: Yang, Gang CTR US USA [mailto:gang.y...@us.army.mil] > Sent: Thursday, March 24, 2011 5:10 PM > To: dev@tuscany.apache.org > Subject: RE: 2.x Policy interceptors - was: Re: PolicyHandler exception > handling issue - PolicyHandler.afterInvoke() is not called when > SOAPFault is generated (UNCLASSIFIED) > > Classification: UNCLASSIFIED > Caveats: NONE > > > > > 1. <binding.ws requires="intent"> did not work for me. In the > debugger, > > the composite builder did recognize the new policy and the fact that > > the > > reference/service has required intent, but matching check failed. > > However, <binding.ws policySets="policyset"> worked. > > > Never mind about the first issue. I had both > createInterceptor(Operation) and createBindingInterceptor() defined so > on the service side, both are activated for service.policy and > service.binding.policy phases. > > However, the same policy extension is used on the reference side and > the > policy interceptor is called only once. I remember I had problems with > activating the policy interceptor on the reference side (before I > played > with service side) if I only define createInterceptor(Operation). So I > defined both to get reference side working. Now with both defined, it > is > called twice on service side. A bug on the reference side? I don't seem > to be able to activate the policy interceptor for reference.policy > phase. > > Gang > > Classification: UNCLASSIFIED > Caveats: NONE > Classification: UNCLASSIFIED Caveats: NONE
