November 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3739) Enforce jbossws-spi metadata immutability

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3739: ------------------------------------- Summary: Enforce jbossws-spi metadata immutability Key: JBWS-3739 URL: https://issues.jboss.org/browse/JBWS-3739 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 All jbossws-spi metadata classes should be immutable, to automatically ensure thread safety and allow for achieving JBWS-3708. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3738) Expand WS-Trust / STS test coverage and documentation

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3738: ------------------------------------- Summary: Expand WS-Trust / STS test coverage and documentation Key: JBWS-3738 URL: https://issues.jboss.org/browse/JBWS-3738 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.3 We should possibly cover more WS-Trust/STS scenarios in the testsuite (different SAML tokens, etc.) and expand the documentation accordingly. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3737) Build PolicyAttachmentStore when the first @PolicySets annotation is found

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3737: ------------------------------------- Summary: Build PolicyAttachmentStore when the first @PolicySets annotation is found Key: JBWS-3737 URL: https://issues.jboss.org/browse/JBWS-3737 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.3 Currently the PolicyAttachmentStore is built the first time a WS deployment is processed. We should actually do that only if the deployment contains @PolicySets annotated classes, that is the first time a deployment actually needing the store is processed. See https://community.jboss.org/message/846750#846750 -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3602) Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module

by Thomas Szadel (JIRA)

[ https://issues.jboss.org/browse/JBWS-3602?page=com.atlassian.jira.plugin.... ] Thomas Szadel commented on JBWS-3602: ------------------------------------- Ok. Thanks for your reactivity ! > Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module > --------------------------------------------------------------------------- > > Key: JBWS-3602 > URL: https://issues.jboss.org/browse/JBWS-3602 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.2 > > > The org.jboss.ws.jaxws-client module is missing a dependency on the javax.servlet.api module. That is causing a NCDFE on ServletException when the endpoint destination cannot be matched with the context + url pattern specified in the request. > This is only reproducible using the jbossws-cxf integration w/ spring and having an endpoint whose address declaration in jbossws-cxf.xml is different from the computed address (context + url pattern) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3602) Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3602?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3602: --------------------------------------- Thomas, you're right, this was forgotten. It's most likely late for EAP 6.2 (you can do that locally anyway, it's a minor change in a module.xml file), but I've created a BZ for it: https://bugzilla.redhat.com/show_bug.cgi?id=1033209 Thanks > Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module > --------------------------------------------------------------------------- > > Key: JBWS-3602 > URL: https://issues.jboss.org/browse/JBWS-3602 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.2 > > > The org.jboss.ws.jaxws-client module is missing a dependency on the javax.servlet.api module. That is causing a NCDFE on ServletException when the endpoint destination cannot be matched with the context + url pattern specified in the request. > This is only reproducible using the jbossws-cxf integration w/ spring and having an endpoint whose address declaration in jbossws-cxf.xml is different from the computed address (context + url pattern) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3602) Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module

by Thomas Szadel (JIRA)

[ https://issues.jboss.org/browse/JBWS-3602?page=com.atlassian.jira.plugin.... ] Thomas Szadel commented on JBWS-3602: ------------------------------------- I think you forgot to commit on JBoss EAP 6.2.0 branch as I didn't see the fix in the beta release available on JBoss website :/ Is it possible to fix it on that branch before the Final release ? Thanks > Missing javax.servlet.api dependency in org.jboss.ws.jaxws-client AS module > --------------------------------------------------------------------------- > > Key: JBWS-3602 > URL: https://issues.jboss.org/browse/JBWS-3602 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.2 > > > The org.jboss.ws.jaxws-client module is missing a dependency on the javax.servlet.api module. That is causing a NCDFE on ServletException when the endpoint destination cannot be matched with the context + url pattern specified in the request. > This is only reproducible using the jbossws-cxf integration w/ spring and having an endpoint whose address declaration in jbossws-cxf.xml is different from the computed address (context + url pattern) -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3731) Control and document behavior regarding thread default bus changes depending on client bus selection strategy

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-3731?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda 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: * THREAD_BUS strategy {noformat} 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 | ======================================= {noformat} * NEW_BUS strategy {noformat} 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 | ======================================= {noformat} * TCCL_BUS strategy {noformat} 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: {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} > 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_BUS strategy > {noformat} > 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 | > ======================================= > {noformat} > * NEW_BUS strategy > {noformat} > 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 | > ======================================= > {noformat} > * TCCL_BUS strategy > {noformat} > 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3731) Control and document behavior regarding thread default bus changes depending on client bus selection strategy

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-3731?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda reopened JBWS-3731: ------------------------------------- > 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3731) Control and document behavior regarding thread default bus changes depending on client bus selection strategy

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3731?page=com.atlassian.jira.plugin.... ] 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

11 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3731) Control and document behavior regarding thread default bus changes depending on client bus selection strategy

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3731?page=com.atlassian.jira.plugin.... ] 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: {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} > 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues November 2013