[
https://issues.apache.org/jira/browse/CXF-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809942#comment-13809942
]
Sambit Dikshit commented on CXF-5364:
-------------------------------------
Hi Daniel, If we want to set the bus name as you mentioned above like <cxf:bus
bus="client-bus"/> and <cxf:bus bus="server-bus"/> programatically to an
endpoint, do we have any API exposed through Endpoint or EndpointImpl to set
the specific bus.
Since most of our users already use the <jaxrs:server> definitions where they
dont specify the bus name as such. Asking them to make such changes in their
code base will be tough to control. Instead we are thinking of using lifecycle
listener, we can control this provided we get a handle to set the bus name to a
endpoint. We didn't see any api explicitly available for this. The idea is once
the jar is deployed, it will automatically add the appropriate bus to endpoints
dynamically without the necessity for the people to make changes in their code
base. We can manage it just at app provisioning time in app container.
> 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)
