[jbossws-issues] [JBoss JIRA] (JBWS-3822) Default to TCCL bus strategy for clients running in-container

[Alessio Soldano (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-3822:
----------------------------------
    Description: 
For performance reasons, it makes sense to default to TCCL bus creation strategy on server side (that is, when running in-container). This means JAX-WS clients created on WildFly container will not use the bus linked to the current thread, but the one linked to the current thread context classloader. This effectively reduces the number of client busses by basically limiting it to the number of application deployments as well as prevents possible issues caused by thread pools (bus re-used by different applications...)
See https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheCXFintegration-BusselectionstrategiesforJAXWSclients for details on Bus creation strategies

  was:For performance reasons, it makes sense to default to TCCL bus creation strategy on server side (that is, when running in-container). This means JAX-WS clients created on WildFly container will not use the bus linked to the current thread, but the one linked to the current thread context classloader. This effectively reduces the number of client busses by basically limiting it to the number of application deployments as well as prevents possible issues caused by thread pools (bus re-used by different applications...)



> Default to TCCL bus strategy for clients running in-container
> -------------------------------------------------------------
>
>                 Key: JBWS-3822
>                 URL: https://issues.jboss.org/browse/JBWS-3822
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf
>            Reporter: Alessio Soldano
>            Assignee: Alessio Soldano
>             Fix For: jbossws-cxf-5.0
>
>
> For performance reasons, it makes sense to default to TCCL bus creation strategy on server side (that is, when running in-container). This means JAX-WS clients created on WildFly container will not use the bus linked to the current thread, but the one linked to the current thread context classloader. This effectively reduces the number of client busses by basically limiting it to the number of application deployments as well as prevents possible issues caused by thread pools (bus re-used by different applications...)
> See https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheCXFintegration-BusselectionstrategiesforJAXWSclients for details on Bus creation strategies



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)