[
https://issues.apache.org/jira/browse/CXF-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827875#comment-13827875
]
Sergey Beryozkin commented on CXF-5364:
---------------------------------------
How about something like this:
{code:java}
Bus currentBus = BusFactory.getCurentThreadBus(c);
Bus clientBus = applicationContext.getBean("clientBus");
BusFactory.setCurentThreadBus(clientBus);
try {
// init the client and let it invoke
} finally {
BusFactory.setCurentThreadBus(currentBus);
}
{code}
Re your possible contribution: can you please start a CXF dev thread or open
JIRA with the attached patch ? IF it is a JAX-RS provider then create a pacth
against the rt-rs-extension-providers module with the optional dependencies. If
it is a CXF Data Binding then I guess it is a new data binding module
Cheers
> Multiple cxf buses in the same spring context
> ----------------------------------------------
>
> Key: CXF-5364
> URL: https://issues.apache.org/jira/browse/CXF-5364
> Project: CXF
> Issue Type: Improvement
> Reporter: Raj Anand
> Fix For: NeedMoreInfo
>
>
> We have a client side CXF bus with in/out interceptors and , a server side
> bus with in/out interceptors. If the same service is being used for both
> client side and server side invocations , the 2 buses end up in the same
> spring application context. As a result of this one CXF bus is over-written
> and the interceptor chain for that CXF bus is lost.So how do we manage
> multiple CXF buses in the same application context without the 2 buses
> interfering with each other.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
