November 2013 - jbossws-issues - Jboss List Archives

[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: * 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 | ======================================= 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 default busses with THREAD_BUS strategy |BEFORE client creation | USED for client | AFTER client creation | NULL | NEW | NEW | Bus X | Bus X | Bus X * Thread default busses with NEW_BUS strategy: |BEFORE client creation | USED for client | AFTER client creation | NULL | NEW | NULL | Bus X | NEW | Bus X * Thread default busses with TCCL_BUS strategy: |BEFORE client creation | USED for client | AFTER client creation | NULL | TCCL | NULL | Bus X | TCCL | Bus X > 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 > > 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 | > ======================================= -- 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

10 years, 5 months

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)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3735) Make sure EndpointService services are started before publishing endpoints

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3735?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3735: --------------------------------------- https://github.com/wildfly/wildfly/pull/5490 > Make sure EndpointService services are started before publishing endpoints > -------------------------------------------------------------------------- > > Key: JBWS-3735 > URL: https://issues.jboss.org/browse/JBWS-3735 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > There's a possible race condition between the EndpointService start and the publishing of the servlet serving the endpoint by the web subsystem. That also applies to the EndpointPublish API scenario. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3736) soap:address rewrite does not consider wsdlLocation in SEI @WebService

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3736?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3736: ---------------------------------- Description: There's a bug in the MetadataBuilder that does not use the @WebService(wsdlLocation=...) data from the service endpoint interface when the information is not available in the annotation on the endpoint implementation. The retrieved data is used for the wsdl soap:address rewrite (only), which is hence not working properly when the only wsdlLocation data provided is in the SEI (not in the impl, not in a deployment descriptor). (was: There's a bug in the MetadataBuilder that does not use the @WebService(wsdlLocation=...) data from the service endpoint interface, while it always the same information from the endpoint implementation annotation only. The data retrieved there is used for the wsdl soap:address rewrite only, which is hence not working properly when the only wsdlLocation data provided in the SEI (not in the impl, not in a deployment descriptor).) > soap:address rewrite does not consider wsdlLocation in SEI @WebService > ---------------------------------------------------------------------- > > Key: JBWS-3736 > URL: https://issues.jboss.org/browse/JBWS-3736 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > There's a bug in the MetadataBuilder that does not use the @WebService(wsdlLocation=...) data from the service endpoint interface when the information is not available in the annotation on the endpoint implementation. The retrieved data is used for the wsdl soap:address rewrite (only), which is hence not working properly when the only wsdlLocation data provided is in the SEI (not in the impl, not in a deployment descriptor). -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3736) soap:address rewrite does not consider wsdlLocation in SEI @WebService

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3736: ------------------------------------- Summary: soap:address rewrite does not consider wsdlLocation in SEI @WebService Key: JBWS-3736 URL: https://issues.jboss.org/browse/JBWS-3736 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 There's a bug in the MetadataBuilder that does not use the @WebService(wsdlLocation=...) data from the service endpoint interface, while it always the same information from the endpoint implementation annotation only. The data retrieved there is used for the wsdl soap:address rewrite only, which is hence not working properly when the only wsdlLocation data provided in the SEI (not in the impl, not in a deployment descriptor). -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3735) Make sure EndpointService services are started before publishing endpoints

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3735: ------------------------------------- Summary: Make sure EndpointService services are started before publishing endpoints Key: JBWS-3735 URL: https://issues.jboss.org/browse/JBWS-3735 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 There's a possible race condition between the EndpointService start and the publishing of the servlet serving the endpoint by the web subsystem. That also applies to the EndpointPublish API scenario. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3734) Upgrade to Apache CXF 2.7.8

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3734: ------------------------------------- Summary: Upgrade to Apache CXF 2.7.8 Key: JBWS-3734 URL: https://issues.jboss.org/browse/JBWS-3734 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.3 -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3514) HTTP session scope support

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3514?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3514: ---------------------------------- Fix Version/s: jbossws-cxf-4.4 (was: jbossws-cxf-4.3) > HTTP session scope support > -------------------------- > > Key: JBWS-3514 > URL: https://issues.jboss.org/browse/JBWS-3514 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.4 > > > Solerman Kaplon says: > "Hello everyone, after metro stack got discontinued and CXF becoming the de-facto stack for JbossWS, I'm missing the @HttpSessionScope annotation. Basically, it automatically adds the jsession id to every http response so sessions can be tracked as usual in HTTP. For instance, that allows one to carry CDI/Seam conversations over several WS requests, very useful for rich clients. I would like for something to be included by default in jboss ws to allow for the same level of usability. Right now, the only alternative is to manually fiddle with the webservice context and add the header yourself. Another level of automation would be a Message Handler of Interceptor to do the job. Any other ideas?" > See also: > http://weblogs.java.net/blog/kohsuke/archive/2006/10/bringing_state.html -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3630) Enable CXF Asynch Client HTTP transport

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3630?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3630: ---------------------------------- Fix Version/s: jbossws-cxf-4.4 (was: jbossws-cxf-4.3) > Enable CXF Asynch Client HTTP transport > --------------------------------------- > > Key: JBWS-3630 > URL: https://issues.jboss.org/browse/JBWS-3630 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.4 > > > Starting from 2.7.x series, Apache CXF provides an additional asynch http client implementation: http://cxf.apache.org/docs/asynchronous-client-http-transport.html > The new transport is built on top of Apache HTTP Components HttpAsyncClient (http://hc.apache.org/httpcomponents-asyncclient-dev/index.html) and is automatically enabled (currently for asynch calls only) whenever the cxf-rt-transports-http-hc component is available. That is currently excluded from the dependency tree and not installed on the JBoss AS / WildFly as the HttpAsyncClient it transitively depends on is still at Beta level. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3733) Allow enabling/disabling endpoint metrics

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3733?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3733: ---------------------------------- Description: We need to offer a mechanism for enabling/disabling endpoint metrics. We should probably have an element/attribute in the container DMR for enabling/disabling the metrics. was:We need to offer a mechanism for enabling/disabling endpoint metrics. > Allow enabling/disabling endpoint metrics > ----------------------------------------- > > Key: JBWS-3733 > URL: https://issues.jboss.org/browse/JBWS-3733 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > We need to offer a mechanism for enabling/disabling endpoint metrics. > We should probably have an element/attribute in the container DMR for enabling/disabling the metrics. -- 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

10 years, 5 months

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