March 2017 - jbossws-issues - Jboss List Archives

[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: ------------------------------------------- Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/24 > 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 > Fix For: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final > > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-4061) Change ref org.codehaus.woodstox:woodstox-core-asl to com.fasterxml.woodstox:woodstox-core

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-4061?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-4061: -------------------------------- PR for master branch submitted: https://github.com/jbossws/jbossws-cxf/pull/27 Merged same change into branch, jbossws-cxf-5.1.x > Change ref org.codehaus.woodstox:woodstox-core-asl to com.fasterxml.woodstox:woodstox-core > ------------------------------------------------------------------------------------------ > > Key: JBWS-4061 > URL: https://issues.jboss.org/browse/JBWS-4061 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final > Reporter: R Searls > Assignee: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final > > > In modules/addons/transports/udp/pom.xml change reference > of org.codehaus.woodstox:woodstox-core-asl > to com.fasterxml.woodstox:woodstox-core:jar > In pom.xml remove dependency stmt to org.codehaus.woodstox:woodstox-core-asl > at line 1271 and prop stmt, woodstox-core-asl.version at line 115 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-4061) Change ref org.codehaus.woodstox:woodstox-core-asl to com.fasterxml.woodstox:woodstox-core

by R Searls (JIRA)

R Searls created JBWS-4061: ------------------------------ Summary: Change ref org.codehaus.woodstox:woodstox-core-asl to com.fasterxml.woodstox:woodstox-core Key: JBWS-4061 URL: https://issues.jboss.org/browse/JBWS-4061 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final Reporter: R Searls Assignee: R Searls Priority: Minor Fix For: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final In modules/addons/transports/udp/pom.xml change reference of org.codehaus.woodstox:woodstox-core-asl to com.fasterxml.woodstox:woodstox-core:jar In pom.xml remove dependency stmt to org.codehaus.woodstox:woodstox-core-asl at line 1271 and prop stmt, woodstox-core-asl.version at line 115 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-4060) Exclude org.ow2.asm from cxf-rt-frontend-jaxws in jbossws-cxf-client

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-4060?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-4060: -------------------------------- I merged the same basis changes into branch jbossws-cxf-5.1.x > Exclude org.ow2.asm from cxf-rt-frontend-jaxws in jbossws-cxf-client > -------------------------------------------------------------------- > > Key: JBWS-4060 > URL: https://issues.jboss.org/browse/JBWS-4060 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final > Reporter: R Searls > Assignee: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final > > > The eap product BOM references jbossws-cxf-client. It has a dependency > on cxf-rt-frontend-jaxws which has a dependency on org.ow2.asm we > don't need or use. This ref needs to be excluded in the client > pom so that the BOM does not drag it in. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-4060) Exclude org.ow2.asm from cxf-rt-frontend-jaxws in jbossws-cxf-client

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-4060?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-4060: -------------------------------- submitted PR https://github.com/jbossws/jbossws-cxf/pull/26 against the current master branch. > Exclude org.ow2.asm from cxf-rt-frontend-jaxws in jbossws-cxf-client > -------------------------------------------------------------------- > > Key: JBWS-4060 > URL: https://issues.jboss.org/browse/JBWS-4060 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final > Reporter: R Searls > Assignee: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final > > > The eap product BOM references jbossws-cxf-client. It has a dependency > on cxf-rt-frontend-jaxws which has a dependency on org.ow2.asm we > don't need or use. This ref needs to be excluded in the client > pom so that the BOM does not drag it in. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-4060) Exclude org.ow2.asm from cxf-rt-frontend-jaxws in jbossws-cxf-client

by R Searls (JIRA)

R Searls created JBWS-4060: ------------------------------ Summary: Exclude org.ow2.asm from cxf-rt-frontend-jaxws in jbossws-cxf-client Key: JBWS-4060 URL: https://issues.jboss.org/browse/JBWS-4060 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final Reporter: R Searls Assignee: R Searls Priority: Minor Fix For: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final The eap product BOM references jbossws-cxf-client. It has a dependency on cxf-rt-frontend-jaxws which has a dependency on org.ow2.asm we don't need or use. This ref needs to be excluded in the client pom so that the BOM does not drag it in. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-4054) AbstractServerConfig#setWebServiceHost uses local hostname, then fails on verification

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-4054?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-4054: -------------------------------- No the change to the test is because of the change in https://github.com/jbossws/jbossws-common/blob/master/src/main/java/org/j... And the affects of the hostnamectl I described in the earlier comment. > AbstractServerConfig#setWebServiceHost uses local hostname, then fails on verification > -------------------------------------------------------------------------------------- > > Key: JBWS-4054 > URL: https://issues.jboss.org/browse/JBWS-4054 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-integration > Environment: Wildfly 10.1.0 > Reporter: Daniel Lichtenberger > Assignee: R Searls > Fix For: jbossws-cxf-5.2.0.Final > > > If "0.0.0.0" is passed to AbstractServerConfig#setWebServiceHost, it uses InetAddress.getLocalHost().getHostName() as the server host. This hostname is then verified using AddressUtils#isValidAddress, which uses the strict requirements for public hostnames. > However, it's quite possible to use characters like "_" in local hostnames, so something like "my_desktop" as a hostname (or even non-ASCII characters) will cause this to fail. > For Wildfly, our workaround is to use a specific IP address (like 127.0.0.1) in the "wsdl-host" of standalone.xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3976) Two different versions of ASM artifact in client dependency tree

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3976?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3976: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.6.Final (was: jbossws-cxf-5.1.4.Final) > Two different versions of ASM artifact in client dependency tree > ---------------------------------------------------------------- > > Key: JBWS-3976 > URL: https://issues.jboss.org/browse/JBWS-3976 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Assignee: R Searls > Fix For: jbossws-cxf-5.1.6.Final > > > In dependency tree of jbossws-cxf-client 5.1.3.Final-redhat-2, there are two different versions of ASM artifact: > {noformat} > +- org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.1.4.redhat-1:compile > | +- xml-resolver:xml-resolver:jar:1.2.0.redhat-11:compile > | +- org.ow2.asm:asm:jar:5.0.4:compile > +- asm:asm:jar:3.3.1.redhat-12:compile > {noformat} > It should probably be chosen which one to keep and exclude the other. > See [upstream client tree|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP7-...] and [productized client tree with BOM import|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP7/view/EAP...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-4055) Remove the lines with index element in test configuration groovy script

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4055?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4055: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.8.Final > Remove the lines with index element in test configuration groovy script > ----------------------------------------------------------------------- > > Key: JBWS-4055 > URL: https://issues.jboss.org/browse/JBWS-4055 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.7.Final > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-5.1.8.Final, jbossws-cxf-5.2.0.Final > > > We now have the groovy script to change some specific wildfly configuration element with index : > def securityDomains = root.profile.subsystem.'security-domains'[0] > This isn't the good way to get the element to change, especially there is elytron security domain is added now. This should be changed to check namspace uri to get the target element . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-4054) AbstractServerConfig#setWebServiceHost uses local hostname, then fails on verification

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4054?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4054: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.0.Final > AbstractServerConfig#setWebServiceHost uses local hostname, then fails on verification > -------------------------------------------------------------------------------------- > > Key: JBWS-4054 > URL: https://issues.jboss.org/browse/JBWS-4054 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-integration > Environment: Wildfly 10.1.0 > Reporter: Daniel Lichtenberger > Assignee: R Searls > Fix For: jbossws-cxf-5.2.0.Final > > > If "0.0.0.0" is passed to AbstractServerConfig#setWebServiceHost, it uses InetAddress.getLocalHost().getHostName() as the server host. This hostname is then verified using AddressUtils#isValidAddress, which uses the strict requirements for public hostnames. > However, it's quite possible to use characters like "_" in local hostnames, so something like "my_desktop" as a hostname (or even non-ASCII characters) will cause this to fail. > For Wildfly, our workaround is to use a specific IP address (like 127.0.0.1) in the "wsdl-host" of standalone.xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

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 March 2017