[jbossws-issues] [JBoss JIRA] (JBWS-3731) Control and document behavior regarding thread default bus changes depending on client bus selection strategy
Alessio Soldano (JIRA)
jira-events at lists.jboss.org
Tue Nov 12 05:31:05 EST 2013
[ https://issues.jboss.org/browse/JBWS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922694#comment-12922694 ]
Alessio Soldano commented on JBWS-3731:
---------------------------------------
Updated https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheCXFintegration-BusselectionstrategiesforJAXWSclients section in the doc.
> Control and document behavior regarding thread default bus changes depending on client bus selection strategy
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBWS-3731
> URL: https://issues.jboss.org/browse/JBWS-3731
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf, productization
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-4.2.3
>
>
> With the availability of different client bus selection strategies, we need to clarify if/what changes a client construction applies to the current thread default bus.
> The enforced behavior should be the following:
> * Thread default busses with THREAD_BUS strategy
> |BEFORE client creation | USED for client | AFTER client creation
> | NULL | NEW | NEW
> | X | X | X
>
> * Thread default busses with NEW_BUS strategy:
> |BEFORE client creation | USED for client | AFTER client creation
> | NULL | NEW | NULL
> | X | NEW | X
>
> * Thread default busses with TCCL_BUS strategy:
> |BEFORE client creation | USED for client | AFTER client creation
> | NULL | TCCL | NULL
> | X | TCCL | X
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossws-issues
mailing list