December 2016 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4047) Enable / disable WS statistics does not reset counters

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/JBWS-4047?page=com.atlassian.jira.plugin.... ] Romain Pelisse commented on JBWS-4047: -------------------------------------- See comment on JBEAP-6439 > Enable / disable WS statistics does not reset counters > ------------------------------------------------------ > > Key: JBWS-4047 > URL: https://issues.jboss.org/browse/JBWS-4047 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.5.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > > Enable / disable statistics does not reset counters. > Right now when I enable stats - do some soap requests - disable stats - enable stats again - counters are not on 0 but continue when they were before disabling stats. > I think reset of counters should be done once stats are disabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4047) Enable / disable WS statistics does not reset counters

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/JBWS-4047?page=com.atlassian.jira.plugin.... ] Romain Pelisse updated JBWS-4047: --------------------------------- Git Pull Request: https://github.com/jbossws/jbossws-spi/pull/3, https://github.com/jbossws/jbossws-common/pull/5, https://github.com/jbossws/jbossws-cxf/pull/19 > Enable / disable WS statistics does not reset counters > ------------------------------------------------------ > > Key: JBWS-4047 > URL: https://issues.jboss.org/browse/JBWS-4047 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.5.Final > Reporter: Romain Pelisse > Assignee: Romain Pelisse > > Enable / disable statistics does not reset counters. > Right now when I enable stats - do some soap requests - disable stats - enable stats again - counters are not on 0 but continue when they were before disabling stats. > I think reset of counters should be done once stats are disabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4047) Enable / disable WS statistics does not reset counters

by Romain Pelisse (JIRA)

Romain Pelisse created JBWS-4047: ------------------------------------ Summary: Enable / disable WS statistics does not reset counters Key: JBWS-4047 URL: https://issues.jboss.org/browse/JBWS-4047 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.5.Final Reporter: Romain Pelisse Assignee: Romain Pelisse Enable / disable statistics does not reset counters. Right now when I enable stats - do some soap requests - disable stats - enable stats again - counters are not on 0 but continue when they were before disabling stats. I think reset of counters should be done once stats are disabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4046) PostConstruct method not invoked on web service handler

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/JBWS-4046?page=com.atlassian.jira.plugin.... ] Bartosz Spyrko-Śmietanko updated JBWS-4046: ------------------------------------------- Description: Application defines two identical web service classes placed in different packages and accessed via different paths (defined in web.xml). Both web services use the same handler class. However, the handler's PostConstruct method is only executed for invocations of one of the two web services (expected: for invocations of both web services). Note this is a regression between EAP 6.4.x and 7.0.x. it seems this is caused by how the ServerBeanCustomizer matches endpoints. In EAP 6 this was based on the bean's class, but in EAP 7 it uses the WSDL_SERVICE and WSDL_PORT of the service. The problem happens when there are two endpoints with the same service address, but different paths. Potential solution: https://github.com/jbossws/jbossws-cxf/compare/jbossws-cxf-5.1.x...spyrko... was: Application defines two identical web service classes placed in different packages and accessed via different paths (defined in web.xml). Both web services use the same handler class. However, the handler's PostConstruct method is only executed for invocations of one of the two web services (expected: for invocations of both web services). Note this is a regression between EAP 6.4.x and 7.0.x. it seems this is caused by how the ServerBeanCustomizer matches endpoints. In EAP 6 this was based on the bean's class, but in EAP 7 it uses the WSDL_SERVICE and WSDL_PORT of the service. The problem happens when there are two endpoints with the same service address, but different paths. Potential solution: https://github.com/jbossws/jbossws-cxf/compare/jbossws-cxf-5.1.x...spyrko... > PostConstruct method not invoked on web service handler > ------------------------------------------------------- > > Key: JBWS-4046 > URL: https://issues.jboss.org/browse/JBWS-4046 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.5.Final > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Alessio Soldano > > Application defines two identical web service classes placed in different packages and accessed via different paths (defined in web.xml). Both web services use the same handler class. > However, the handler's PostConstruct method is only executed for invocations of one of the two web services (expected: for invocations of both web services). > Note this is a regression between EAP 6.4.x and 7.0.x. > it seems this is caused by how the ServerBeanCustomizer matches endpoints. In EAP 6 this was based on the bean's class, but in EAP 7 it uses the WSDL_SERVICE and WSDL_PORT of the service. The problem happens when there are two endpoints with the same service address, but different paths. > Potential solution: https://github.com/jbossws/jbossws-cxf/compare/jbossws-cxf-5.1.x...spyrko... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4046) PostConstruct method not invoked on web service handler

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/JBWS-4046?page=com.atlassian.jira.plugin.... ] Bartosz Spyrko-Śmietanko updated JBWS-4046: ------------------------------------------- Description: Application defines two identical web service classes placed in different packages and accessed via different paths (defined in web.xml). Both web services use the same handler class. However, the handler's PostConstruct method is only executed for invocations of one of the two web services (expected: for invocations of both web services). Note this is a regression between EAP 6.4.x and 7.0.x. it seems this is caused by how the ServerBeanCustomizer matches endpoints. In EAP 6 this was based on the bean's class, but in EAP 7 it uses the WSDL_SERVICE and WSDL_PORT of the service. The problem happens when there are two endpoints with the same service address, but different paths. Potential solution: https://github.com/jbossws/jbossws-cxf/compare/jbossws-cxf-5.1.x...spyrko... was: Application defines two identical web service classes placed in different packages and accessed via different paths (defined in web.xml). Both web services use the same handler class. However, the handler's PostConstruct method is only executed for invocations of one of the two web services (expected: for invocations of both web services). Note this is a regression between EAP 6.4.x and 7.0.x. it seems this is caused by how the ServerBeanCustomizer matches endpoints. In EAP 6 this was based on the bean's class, but in EAP 7 it uses the WSDL_SERVICE and WSDL_PORT of the service. The problem happens when there are two endpoints with the same service address, but different paths. Potential solution: > PostConstruct method not invoked on web service handler > ------------------------------------------------------- > > Key: JBWS-4046 > URL: https://issues.jboss.org/browse/JBWS-4046 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.5.Final > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Alessio Soldano > > Application defines two identical web service classes placed in different packages and accessed via different paths (defined in web.xml). Both web services use the same handler class. > However, the handler's PostConstruct method is only executed for invocations of one of the two web services (expected: for invocations of both web services). > Note this is a regression between EAP 6.4.x and 7.0.x. > it seems this is caused by how the ServerBeanCustomizer matches endpoints. In EAP 6 this was based on the bean's class, but in EAP 7 it uses the WSDL_SERVICE and WSDL_PORT of the service. The problem happens when there are two endpoints with the same service address, but different paths. > Potential solution: https://github.com/jbossws/jbossws-cxf/compare/jbossws-cxf-5.1.x...spyrko... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4046) PostConstruct method not invoked on web service handler

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/JBWS-4046?page=com.atlassian.jira.plugin.... ] Bartosz Spyrko-Śmietanko updated JBWS-4046: ------------------------------------------- Assignee: Alessio Soldano > PostConstruct method not invoked on web service handler > ------------------------------------------------------- > > Key: JBWS-4046 > URL: https://issues.jboss.org/browse/JBWS-4046 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.5.Final > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Alessio Soldano > > Application defines two identical web service classes placed in different packages and accessed via different paths (defined in web.xml). Both web services use the same handler class. > However, the handler's PostConstruct method is only executed for invocations of one of the two web services (expected: for invocations of both web services). > Note this is a regression between EAP 6.4.x and 7.0.x. > it seems this is caused by how the ServerBeanCustomizer matches endpoints. In EAP 6 this was based on the bean's class, but in EAP 7 it uses the WSDL_SERVICE and WSDL_PORT of the service. The problem happens when there are two endpoints with the same service address, but different paths. > Potential solution: -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4046) PostConstruct method not invoked on web service handler

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created JBWS-4046: ---------------------------------------------- Summary: PostConstruct method not invoked on web service handler Key: JBWS-4046 URL: https://issues.jboss.org/browse/JBWS-4046 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.5.Final Reporter: Bartosz Spyrko-Śmietanko Application defines two identical web service classes placed in different packages and accessed via different paths (defined in web.xml). Both web services use the same handler class. However, the handler's PostConstruct method is only executed for invocations of one of the two web services (expected: for invocations of both web services). Note this is a regression between EAP 6.4.x and 7.0.x. it seems this is caused by how the ServerBeanCustomizer matches endpoints. In EAP 6 this was based on the bean's class, but in EAP 7 it uses the WSDL_SERVICE and WSDL_PORT of the service. The problem happens when there are two endpoints with the same service address, but different paths. Potential solution: -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4045) Upgrade woodstox to 5.x (more changes)

by R Searls (JIRA)

R Searls created JBWS-4045: ------------------------------ Summary: Upgrade woodstox to 5.x (more changes) Key: JBWS-4045 URL: https://issues.jboss.org/browse/JBWS-4045 Project: JBoss Web Services Issue Type: Feature Request Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.5.Final Reporter: R Searls Assignee: R Searls Priority: Minor Fix For: jbossws-cxf-5.1.6.Final Update version so we are in sync with EAP 7.x usage. QA requested additional changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4038) few exceptions are ignored, trace level logging should be better option

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4038?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-4038: --------------------------------------- Feel free to create a new jira for the latest additions, if you really feel there's need for tracking them explicitly (I don't think so in this case). > few exceptions are ignored, trace level logging should be better option > ----------------------------------------------------------------------- > > Key: JBWS-4038 > URL: https://issues.jboss.org/browse/JBWS-4038 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.5.Final > Reporter: R Searls > Assignee: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.1.6.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4044) Upgrade to Apache Santuario 2.0.8

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-4044: ------------------------------------- Summary: Upgrade to Apache Santuario 2.0.8 Key: JBWS-4044 URL: https://issues.jboss.org/browse/JBWS-4044 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.2.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 12 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 December 2016