[
https://issues.apache.org/jira/browse/CXF-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823818#comment-13823818
]
Sergey Beryozkin commented on CXF-5364:
---------------------------------------
I'm sorry, I just don't follow. I'm confused about what is it that you try to
configure around CXF interceptors that does not work with what CXF already
supports.
FYI, endpoint or client level interceptors would not override bus-level
interceptors.
So we have several options. One option is to have multiple buses, that seems
clean enough, or we can isolate interceptors to specific endpoints or clients
with the bus interceptors being added to the complete set of interceptors used
by a given endpoint or client. I don't understand why neither of these options
can work in your case.
I'd really like to see the basic, not related to your production case, Spring
configuration, emulating the problem, showing the basic server & client Spring
configuration where the interceptors are actually lost.
Sergey
> 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)
