[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 19 11:00:07 EST 2013
[ https://issues.jboss.org/browse/JBWS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano updated JBWS-3731:
----------------------------------
Description:
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:
{noformat}
* * THREAD_BUS strategy
*
* Bus used for client
* =======================================
* | | Client Bus |
* =======================================
* | Default | NULL | New bus (Z) |
* | Thread |-------------------------|
* | Bus | Bus X | Bus X |
* =======================================
*
* State of buses before and after client creation
* =======================================
* | Bus | BEFORE | AFTER |
* =======================================
* | Default | NULL | New bus (Z) |
* | Thread |--------------------------|
* | Bus | Bus X | Bus X |
* =======================================
* | TCCL | NULL | NULL |
* | Bus |--------------------------|
* | | Bus Y | Bus Y |
* =======================================
*
*
* * NEW_BUS strategy
*
* Bus used for client
* =======================================
* | | Client Bus |
* =======================================
* | Default | NULL | New bus |
* | Thread |-------------------------|
* | Bus | Bus X | New bus |
* =======================================
*
* State of buses before and after client creation
* =======================================
* | Bus | BEFORE | AFTER |
* =======================================
* | Default | NULL | NULL |
* | Thread |--------------------------|
* | Bus | Bus X | Bus X |
* =======================================
* | TCCL | NULL | NULL |
* | Bus |--------------------------|
* | | Bus Y | Bus Y |
* =======================================
*
*
* * TCCL_BUS strategy
*
* Bus used for client
* =======================================
* | | Client Bus |
* =======================================
* | TCCL | NULL | New bus (Z) |
* | Bus |-------------------------|
* | | Bus Y | Bus Y |
* =======================================
*
* State of buses before and after client creation
* =======================================
* | Bus | BEFORE | AFTER |
* =======================================
* | Default | NULL | NULL |
* | Thread |--------------------------|
* | Bus | Bus X | Bus X |
* =======================================
* | TCCL | NULL | New bus (Z) |
* | Bus |--------------------------|
* | | Bus Y | Bus Y |
* =======================================
{noformat}
was:
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_BUS strategy
Bus used for client
=======================================
| | Client Bus |
=======================================
| Default | NULL | New bus (Z) |
| Thread |-------------------------|
| Bus | Bus X | Bus X |
=======================================
State of buses before and after client creation
=======================================
| Bus | BEFORE | AFTER |
=======================================
| Default | NULL | New bus (Z) |
| Thread |--------------------------|
| Bus | Bus X | Bus X |
=======================================
| TCCL | NULL | NULL |
| Bus |--------------------------|
| | Bus Y | Bus Y |
=======================================
* NEW_BUS strategy
Bus used for client
=======================================
| | Client Bus |
=======================================
| Default | NULL | New bus |
| Thread |-------------------------|
| Bus | Bus X | New bus |
=======================================
State of buses before and after client creation
=======================================
| Bus | BEFORE | AFTER |
=======================================
| Default | NULL | NULL |
| Thread |--------------------------|
| Bus | Bus X | Bus X |
=======================================
| TCCL | NULL | NULL |
| Bus |--------------------------|
| | Bus Y | Bus Y |
=======================================
* TCCL_BUS strategy
Bus used for client
=======================================
| | Client Bus |
=======================================
| TCCL | NULL | New bus (Z) |
| Bus |-------------------------|
| | Bus Y | Bus Y |
=======================================
State of buses before and after client creation
=======================================
| Bus | BEFORE | AFTER |
=======================================
| Default | NULL | NULL |
| Thread |--------------------------|
| Bus | Bus X | Bus X |
=======================================
| TCCL | NULL | New bus (Z) |
| Bus |--------------------------|
| | Bus Y | Bus Y |
=======================================
> 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:
> {noformat}
> * * THREAD_BUS strategy
> *
> * Bus used for client
> * =======================================
> * | | Client Bus |
> * =======================================
> * | Default | NULL | New bus (Z) |
> * | Thread |-------------------------|
> * | Bus | Bus X | Bus X |
> * =======================================
> *
> * State of buses before and after client creation
> * =======================================
> * | Bus | BEFORE | AFTER |
> * =======================================
> * | Default | NULL | New bus (Z) |
> * | Thread |--------------------------|
> * | Bus | Bus X | Bus X |
> * =======================================
> * | TCCL | NULL | NULL |
> * | Bus |--------------------------|
> * | | Bus Y | Bus Y |
> * =======================================
> *
> *
> * * NEW_BUS strategy
> *
> * Bus used for client
> * =======================================
> * | | Client Bus |
> * =======================================
> * | Default | NULL | New bus |
> * | Thread |-------------------------|
> * | Bus | Bus X | New bus |
> * =======================================
> *
> * State of buses before and after client creation
> * =======================================
> * | Bus | BEFORE | AFTER |
> * =======================================
> * | Default | NULL | NULL |
> * | Thread |--------------------------|
> * | Bus | Bus X | Bus X |
> * =======================================
> * | TCCL | NULL | NULL |
> * | Bus |--------------------------|
> * | | Bus Y | Bus Y |
> * =======================================
> *
> *
> * * TCCL_BUS strategy
> *
> * Bus used for client
> * =======================================
> * | | Client Bus |
> * =======================================
> * | TCCL | NULL | New bus (Z) |
> * | Bus |-------------------------|
> * | | Bus Y | Bus Y |
> * =======================================
> *
> * State of buses before and after client creation
> * =======================================
> * | Bus | BEFORE | AFTER |
> * =======================================
> * | Default | NULL | NULL |
> * | Thread |--------------------------|
> * | Bus | Bus X | Bus X |
> * =======================================
> * | TCCL | NULL | New bus (Z) |
> * | Bus |--------------------------|
> * | | Bus Y | Bus Y |
> * =======================================
> {noformat}
--
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