I'm not sure how to do that, but you can also attach interceptors to specific web service providers instead of at the bus-level, so the interceptors would not be called except for incoming calls to those particular services. That might work for you.
Glen Chris Hardin wrote: > > How would that work? How could I configure to separate the client and > server > calls?? > > On Wed, Jun 2, 2010 at 10:25 AM, Benson Margulies > <[email protected]>wrote: > >> I think that you will need to set up two busses. >> >> On Wed, Jun 2, 2010 at 11:08 AM, Chris Hardin <[email protected]> >> wrote: >> > I have the config below. I have a huge problem though. The interceptors >> are >> > not only firing when someone calls my services, they also fire when I >> call >> > another service. I only want these interceptors to fire for the >> services >> > that I have exposed and not the ones I call out to another ESB for. >> > >> > <cxf:bus> >> > >> > <cxf:inInterceptors> >> > <ref bean="timerIn"/> >> > <ref bean="openSessionIn"/> >> > </cxf:inInterceptors> >> > <cxf:outInterceptors> >> > >> > <ref bean="openSessionOut"/> >> > <ref bean="timerOut"/> >> > </cxf:outInterceptors> >> > >> > <cxf:features> >> > <cxf:logging /> >> > <cxf:fastinfoset/> >> > <!-- <ref bean="gzipFeature"/>--> >> > >> > </cxf:features> >> > >> > <cxf:properties> >> > >> > <entry key="schema-validation-enabled" value="false" /> >> > </cxf:properties> >> > >> > </cxf:bus> >> > >> > > -- View this message in context: http://old.nabble.com/Help%21-My-interceptors-fire-for-client-calls-tp28755929p28756966.html Sent from the cxf-user mailing list archive at Nabble.com.
