[jbossws-issues] [JBoss JIRA] (JBWS-3822) Default to TCCL bus strategy for clients running in-container
Alessio Soldano (JIRA)
issues at jboss.org
Mon Aug 25 11:45:00 EDT 2014
Alessio Soldano created JBWS-3822:
-------------------------------------
Summary: 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...)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jbossws-issues
mailing list