[ 
https://issues.apache.org/jira/browse/CXF-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026256#comment-16026256
 ] 

Sergey Beryozkin commented on CXF-7383:
---------------------------------------

Hi, please ask the questions at the CXF users list. FYI, CXFServlet has a 'bus' 
servlet property. One would need to have 2 CXFServlets, one per bus. => 
different servlet URL patterns. The simpler option might be to have a single 
bus.  

> Supporting multiple end points with different bus
> -------------------------------------------------
>
>                 Key: CXF-7383
>                 URL: https://issues.apache.org/jira/browse/CXF-7383
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 3.1.7
>            Reporter: Tony Clarke
>
> Hi,
> If we define two buses in xml configuration
> <cxf:bus name="cxf-abstract-bus" 
>               abstract="true">
> </cxf:bus>
> <bean id="cxf-usernametoken" abstract="true" parent="cxf-abstract-bus">
>               <property name="inInterceptors">
>                       <list>
>                               <ref bean="userNameTokenInterceptor" />
>                       </list>
>               </property>
> </bean>
> <bean id="cxf-samltokensigned" abstract="true" parent="cxf-abstract-bus">
>               <property name="inInterceptors">
>                       <list>
>                               <ref bean="samlTokenSignedInterceptor" />
>                       </list>
>               </property>
> </bean>
> <bean id="cxf" parent="cxf-usernametoken"/>
>       
> <bean id="cxf-saml-bus" parent="cxf-samltokensignaturesigned" />
> Now we have two endpoint definitions:
> <jaxws:endpoint bus="cxf"
> ....
> </jaxws:endpoint>
> <jaxws:endpoint bus="cxf-saml-bus"
> ....
> </jaxws:endpoint>
> Is it expected to work? Currently we are experiencing a situation where we 
> can only define one bus and use it across all endpoints. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to