Hi Sergey,
That sounds potentially doable, but I'm not sure of how I'd go about it.
Our web service isn't defined within configuration, but we do define a
client to make calls out to another service (which is where the
headerInterceptor needs to execute) which we define as follows:
(The roundRobinAddresses is just a bean within the config file, I don't
think it should cause us problems)
<jaxws:client id="bonusServiceClient"
serviceClass="BonusServicePortType"
address="...">
<jaxws:features>
<clustering:failover>
<clustering:strategy>
<ref bean="roundRobinAddresses" />
</clustering:strategy>
</clustering:failover>
</jaxws:features>
</jaxws:client>
Should I be able to add some outInterceptors into this client definition and
it all just work fine? So something like the following:
<jaxws:client id="bonusServiceClient"
serviceClass="BonusServicePortType"
address="...">
<jaxws:features>
<clustering:failover>
<clustering:strategy>
<ref bean="roundRobinAddresses" />
</clustering:strategy>
</clustering:failover>
</jaxws:features>
<jaxws:outInterceptors>
<ref bean="headerInterceptor" />
</jaxws:outInterceptors>
</jaxws:client>
I'm trying this out now, but our test mechanism is a bit slow on the turn
around.
Cheers,
Dan
--
View this message in context:
http://cxf.547215.n5.nabble.com/Configuring-Interceptors-in-Multiple-Spring-Config-Files-tp5736041p5736066.html
Sent from the cxf-user mailing list archive at Nabble.com.
