January 2017 - jbossws-issues - Jboss List Archives

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

by Daniel Lichtenberger (JIRA)

Daniel Lichtenberger created JBWS-4054: ------------------------------------------ Summary: 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 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4053) Build broken against WFLY master due to 'plain-text' attribute moved from 'security-realms' to 'properties-realm'

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-4053: ------------------------------------- Summary: Build broken against WFLY master due to 'plain-text' attribute moved from 'security-realms' to 'properties-realm' Key: JBWS-4053 URL: https://issues.jboss.org/browse/JBWS-4053 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf, jbossws-integration 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, 11 months

1
0
0 / 0

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

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4046?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4046: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.8.Final jbossws-cxf-5.2.0.Final > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4052) Maven build is unnecessarily updating org.eclipse.* dependencies everytime

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-4052?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4052: ------------------------------ Priority: Minor (was: Major) > Maven build is unnecessarily updating org.eclipse.* dependencies everytime > -------------------------------------------------------------------------- > > Key: JBWS-4052 > URL: https://issues.jboss.org/browse/JBWS-4052 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, productization > Affects Versions: jbossws-cxf-5.1.7.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Minor > > Maven build is unnecessarily updating org.eclipse.* dependencies everytime which could prolong the execution by several minutes just to wait for connections to timeout (depending on current environment setup). > {code:java} > [INFO] Scanning for projects... > Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/css/core/maven-metadata... > Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/css/core/maven-metadat... > [WARNING] Could not transfer metadata org.eclipse.wst.css:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Could not transfer metadata org.eclipse.wst.css:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/sse/core/maven-metadat... > Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/sse/core/maven-metadata... > [WARNING] Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/common/uriresolver/mav... > Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/common/uriresolver/mave... > [WARNING] Could not transfer metadata org.eclipse.wst.common:uriresolver/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Could not transfer metadata org.eclipse.wst.common:uriresolver/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > [WARNING] Failure to transfer org.eclipse.wst.sse:core/maven-metadata.xml from http://repository.jboss.com/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of repository.jboss.com has elapsed or updates are forced. Original error: Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Failure to transfer org.eclipse.wst.sse:core/maven-metadata.xml from http://download.java.net/maven/1 was cached in the local repository, resolution will not be reattempted until the update interval of maven-repository.dev.java.net has elapsed or updates are forced. Original error: Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > [INFO] ------------------------------------------------------------------------ > {code} > This is caused by issue with maven-jdocbook-plugin PRESSGANG-60. > There are two basic solutions to this: > # only exclude org.eclipse.* dependencies in plugin dependency management since they are not used anyway (info from the PRESSGANG-60) > # do a full update of maven-jdocbook-plugin to latest version along with usage of new org.jboss.pressgang extensions instead of current org.jboss:jbossorg-jdocbook* ones -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4052) Maven build is unnecessarily updating org.eclipse.* dependencies everytime

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-4052?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4052: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/22 Assignee: Jan Blizňák I sent a PR https://github.com/jbossws/jbossws-cxf/pull/22 with the solution #1 which is less invasive, no new dependencies. I can prepare a PR for #2 too if evaluated as better solution. > Maven build is unnecessarily updating org.eclipse.* dependencies everytime > -------------------------------------------------------------------------- > > Key: JBWS-4052 > URL: https://issues.jboss.org/browse/JBWS-4052 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, productization > Affects Versions: jbossws-cxf-5.1.7.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > > Maven build is unnecessarily updating org.eclipse.* dependencies everytime which could prolong the execution by several minutes just to wait for connections to timeout (depending on current environment setup). > {code:java} > [INFO] Scanning for projects... > Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/css/core/maven-metadata... > Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/css/core/maven-metadat... > [WARNING] Could not transfer metadata org.eclipse.wst.css:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Could not transfer metadata org.eclipse.wst.css:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/sse/core/maven-metadat... > Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/sse/core/maven-metadata... > [WARNING] Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/common/uriresolver/mav... > Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/common/uriresolver/mave... > [WARNING] Could not transfer metadata org.eclipse.wst.common:uriresolver/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Could not transfer metadata org.eclipse.wst.common:uriresolver/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > [WARNING] Failure to transfer org.eclipse.wst.sse:core/maven-metadata.xml from http://repository.jboss.com/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of repository.jboss.com has elapsed or updates are forced. Original error: Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) > [WARNING] Failure to transfer org.eclipse.wst.sse:core/maven-metadata.xml from http://download.java.net/maven/1 was cached in the local repository, resolution will not be reattempted until the update interval of maven-repository.dev.java.net has elapsed or updates are forced. Original error: Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory > [INFO] ------------------------------------------------------------------------ > {code} > This is caused by issue with maven-jdocbook-plugin PRESSGANG-60. > There are two basic solutions to this: > # only exclude org.eclipse.* dependencies in plugin dependency management since they are not used anyway (info from the PRESSGANG-60) > # do a full update of maven-jdocbook-plugin to latest version along with usage of new org.jboss.pressgang extensions instead of current org.jboss:jbossorg-jdocbook* ones -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4052) Maven build is unnecessarily updating org.eclipse.* dependencies everytime

by Jan Blizňák (JIRA)

Jan Blizňák created JBWS-4052: --------------------------------- Summary: Maven build is unnecessarily updating org.eclipse.* dependencies everytime Key: JBWS-4052 URL: https://issues.jboss.org/browse/JBWS-4052 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf, productization Affects Versions: jbossws-cxf-5.1.7.Final Reporter: Jan Blizňák Maven build is unnecessarily updating org.eclipse.* dependencies everytime which could prolong the execution by several minutes just to wait for connections to timeout (depending on current environment setup). {code:java} [INFO] Scanning for projects... Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/css/core/maven-metadata... Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/css/core/maven-metadat... [WARNING] Could not transfer metadata org.eclipse.wst.css:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) [WARNING] Could not transfer metadata org.eclipse.wst.css:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/sse/core/maven-metadat... Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/sse/core/maven-metadata... [WARNING] Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) [WARNING] Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory Downloading: http://repository.jboss.com/maven2/org/eclipse/wst/common/uriresolver/mav... Downloading: http://snapshots.jboss.org/maven2/org/eclipse/wst/common/uriresolver/mave... [WARNING] Could not transfer metadata org.eclipse.wst.common:uriresolver/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) [WARNING] Could not transfer metadata org.eclipse.wst.common:uriresolver/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory [WARNING] Failure to transfer org.eclipse.wst.sse:core/maven-metadata.xml from http://repository.jboss.com/maven2/ was cached in the local repository, resolution will not be reattempted until the update interval of repository.jboss.com has elapsed or updates are forced. Original error: Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to repository.jboss.com (http://repository.jboss.com/maven2/): Connect to repository.jboss.com:80 [repository.jboss.com/10.5.105.13] failed: Connection timed out (Connection timed out) [WARNING] Failure to transfer org.eclipse.wst.sse:core/maven-metadata.xml from http://download.java.net/maven/1 was cached in the local repository, resolution will not be reattempted until the update interval of maven-repository.dev.java.net has elapsed or updates are forced. Original error: Could not transfer metadata org.eclipse.wst.sse:core/maven-metadata.xml from/to maven-repository.dev.java.net (http://download.java.net/maven/1): Cannot access http://download.java.net/maven/1 with type legacy using the available connector factories: BasicRepositoryConnectorFactory [INFO] ------------------------------------------------------------------------ {code} This is caused by issue with maven-jdocbook-plugin PRESSGANG-60. There are two basic solutions to this: # only exclude org.eclipse.* dependencies in plugin dependency management since they are not used anyway (info from the PRESSGANG-60) # do a full update of maven-jdocbook-plugin to latest version along with usage of new org.jboss.pressgang extensions instead of current org.jboss:jbossorg-jdocbook* ones -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3989) JBossWS 5.1.4.Final, JBossWS 5.1.5.Final, JBossWS 5.1.6.Final, JBossWS 5.1.7.Final errata

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3989?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3989 at 1/19/17 6:10 PM: ---------------------------------------------------------------- JBossWS 5.1.4.Final and 5.1.5.Final ---------------------------------------------- WildFly 9.0.1.Final, WildFly 9.0.2.Final, WildFly 10.0.0.Final: * JBWS-3702 FIXME: Add support for https protocol * JBWS-3620 Authentication failures w/ Undertow * FIXME: [CXF-1519] Explicitely set the namespace of a WebFault * FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding * FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol * JBWS-2480 Soap attachments are dropped on server response * JBWS-2561 XOP request not properly inlined * Tests migrated from JBossWS-Native specific testsuite which are meant to pass with JBossWS-CXF too, but are still to be fixed JBossWS 5.1.6.Final and JBossWS 5.1.7.Final ----------------------------------------------------------- WildFly 9.0.2.Final, WildFly 10.0.0.Final, WildFly 10.1.0.Final: * JBWS-3702 FIXME: Add support for https protocol * JBWS-3620 Authentication failures w/ Undertow * FIXME: [CXF-1519] Explicitely set the namespace of a WebFault * FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding * FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol * JBWS-2480 Soap attachments are dropped on server response * JBWS-2561 XOP request not properly inlined * Tests migrated from JBossWS-Native specific testsuite which are meant to pass with JBossWS-CXF too, but are still to be fixed was (Author: asoldano): JBossWS 5.1.4.Final and 5.1.5.Final ---------------------------------------------- WildFly 9.0.1.Final, WildFly 9.0.2.Final, WildFly 10.0.0.Final: * JBWS-3702 FIXME: Add support for https protocol * JBWS-3620 Authentication failures w/ Undertow * FIXME: [CXF-1519] Explicitely set the namespace of a WebFault * FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding * FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol * JBWS-2480 Soap attachments are dropped on server response * JBWS-2561 XOP request not properly inlined * Tests migrated from JBossWS-Native specific testsuite which are meant to pass with JBossWS-CXF too, but are still to be fixed JBossWS 5.1.6.Final ---------------------------------------------- WildFly 9.0.2.Final, WildFly 10.0.0.Final, WildFly 10.1.0.Final: * JBWS-3702 FIXME: Add support for https protocol * JBWS-3620 Authentication failures w/ Undertow * FIXME: [CXF-1519] Explicitely set the namespace of a WebFault * FIXME: [CXF-2531] Wrong "transport" attribute in soap12:binding * FIXME: [CXF-4600] Exception inheritance not working over SOAP protocol * JBWS-2480 Soap attachments are dropped on server response * JBWS-2561 XOP request not properly inlined * Tests migrated from JBossWS-Native specific testsuite which are meant to pass with JBossWS-CXF too, but are still to be fixed > JBossWS 5.1.4.Final, JBossWS 5.1.5.Final, JBossWS 5.1.6.Final, JBossWS 5.1.7.Final errata > ----------------------------------------------------------------------------------------- > > Key: JBWS-3989 > URL: https://issues.jboss.org/browse/JBWS-3989 > Project: JBoss Web Services > Issue Type: Task > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.4.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3989) JBossWS 5.1.4.Final, JBossWS 5.1.5.Final, JBossWS 5.1.6.Final, JBossWS 5.1.7.Final errata

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3989?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3989: ---------------------------------- Summary: JBossWS 5.1.4.Final, JBossWS 5.1.5.Final, JBossWS 5.1.6.Final, JBossWS 5.1.7.Final errata (was: JBossWS 5.1.4.Final, JBossWS 5.1.5.Final and JBossWS 5.1.6.Final errata) > JBossWS 5.1.4.Final, JBossWS 5.1.5.Final, JBossWS 5.1.6.Final, JBossWS 5.1.7.Final errata > ----------------------------------------------------------------------------------------- > > Key: JBWS-3989 > URL: https://issues.jboss.org/browse/JBWS-3989 > Project: JBoss Web Services > Issue Type: Task > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.4.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3989) JBossWS 5.1.4.Final, JBossWS 5.1.5.Final and JBossWS 5.1.6.Final errata

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3989?page=com.atlassian.jira.plugin.... ] Alessio Soldano reopened JBWS-3989: ----------------------------------- > JBossWS 5.1.4.Final, JBossWS 5.1.5.Final and JBossWS 5.1.6.Final errata > ----------------------------------------------------------------------- > > Key: JBWS-3989 > URL: https://issues.jboss.org/browse/JBWS-3989 > Project: JBoss Web Services > Issue Type: Task > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.4.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4028) Upgrade to Apache WSS4J 2.1.8

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4028?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4028: ---------------------------------- Issue Type: Component Upgrade (was: Task) > Upgrade to Apache WSS4J 2.1.8 > ----------------------------- > > Key: JBWS-4028 > URL: https://issues.jboss.org/browse/JBWS-4028 > Project: JBoss Web Services > Issue Type: Component Upgrade > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.7.Final > > > Upgrade to Apache WSS4J 2.1.8, in particular to pull fix for https://issues.apache.org/jira/browse/WSS-587 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 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 January 2017