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

[ https://issues.jboss.org/browse/JBWS-3822?page=com.atlassian.jira.plugin.... ] 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#ApacheC... 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...) -- This message was sent by Atlassian JIRA (v6.3.1#6329)