April 2019 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4167) jdk-11 updates required to project jaxws-undertow-httpspi

by r searls (Jira)

r searls created JBWS-4167: ------------------------------ Summary: jdk-11 updates required to project jaxws-undertow-httpspi Key: JBWS-4167 URL: https://issues.jboss.org/browse/JBWS-4167 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jaxws-undertow-httpspi-1.0.2.final Reporter: r searls Assignee: r searls Maven dependences need to be added to support build with jdk-11 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4166) exclude rome:rome:1.0 so more current version will be used

by r searls (Jira)

r searls created JBWS-4166: ------------------------------ Summary: exclude rome:rome:1.0 so more current version will be used Key: JBWS-4166 URL: https://issues.jboss.org/browse/JBWS-4166 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Reporter: r searls Assignee: r searls rome:rome:1.0 is pulled in by <groupId>org.apache.jmeter</groupId> <artifactId>ApacheJMeter_java</artifactId> rome:rome:1.0 was release 2010-05-10. There are more current versions available. Exclude rome:rome:1.0 in ApacheJMeter_java so more current version will be used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4154) jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4154?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-4154: ------------------------------ [~rsearls] It looks rome dependency is imported from jmeter dependency. Did you try with add rome exclusion from the jmeter dependency ? > jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec > ---------------------------------------------------------------------------------------- > > Key: JBWS-4154 > URL: https://issues.jboss.org/browse/JBWS-4154 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: r searls > Priority: Major > Fix For: jbossws-cxf-5.3.0.Final > > > dependency:tree goal output shows that jbossws-cxf-client (and transitively other modules too) depends on two versions of JBoss JAX-WS API: > org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile > org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.3_spec:jar:1.0.0.Final:compile > The former is brought in by: > {code:java} > +- org.jboss.ws.cxf:jbossws-cxf-transports-undertow:jar:5.2.5-SNAPSHOT:compile > | \- org.jboss.ws.projects:jaxws-undertow-httpspi:jar:1.0.1.Final:compile > | +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile > {code} > I guess we should stick to the newer one which would mean add some dependency exclude or update jaxws-undertow-httpspi to new API version stream (I vote for this) > Whole dependency tree at https://github.com/jbliznak/jbws-dependency-trees/blob/jdk11-after/jbossw... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4133) Deal with java.security.acl classes being removed in Java 13

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4133?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-4133: ------------------------------ Thanks for update, Rebecca. Let us go back to look at this when JBossWS/CXF supports JDK-13. > Deal with java.security.acl classes being removed in Java 13 > ------------------------------------------------------------ > > Key: JBWS-4133 > URL: https://issues.jboss.org/browse/JBWS-4133 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: r searls > Priority: Major > > See https://issues.apache.org/jira/browse/CXF-7815 / https://bugs.openjdk.java.net/browse/JDK-8191138 . > We also make direct use of Group in our SubjectCreatingInterceptors, which are extensions of CXF ones. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4133) Deal with java.security.acl classes being removed in Java 13

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4133?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-4133: ------------------------- Fix Version/s: (was: jbossws-cxf-5.3.0.Final) > Deal with java.security.acl classes being removed in Java 13 > ------------------------------------------------------------ > > Key: JBWS-4133 > URL: https://issues.jboss.org/browse/JBWS-4133 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: r searls > Priority: Major > > See https://issues.apache.org/jira/browse/CXF-7815 / https://bugs.openjdk.java.net/browse/JDK-8191138 . > We also make direct use of Group in our SubjectCreatingInterceptors, which are extensions of CXF ones. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4133) Deal with java.security.acl classes being removed in Java 13

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4133?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-4133: ------------------------- Summary: Deal with java.security.acl classes being removed in Java 13 (was: Deal with java.security.acl classes being removed in Java 12) > Deal with java.security.acl classes being removed in Java 13 > ------------------------------------------------------------ > > Key: JBWS-4133 > URL: https://issues.jboss.org/browse/JBWS-4133 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: r searls > Priority: Major > Fix For: jbossws-cxf-5.3.0.Final > > > See https://issues.apache.org/jira/browse/CXF-7815 / https://bugs.openjdk.java.net/browse/JDK-8191138 . > We also make direct use of Group in our SubjectCreatingInterceptors, which are extensions of CXF ones. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4154) jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec

by r searls (Jira)

[ https://issues.jboss.org/browse/JBWS-4154?page=com.atlassian.jira.plugin.... ] r searls commented on JBWS-4154: -------------------------------- Jim, I resolved my maven-enforcer issue. Something in my env. A different issue however, I had trouble running the integration-tests. I got the error that jbossws-cxf-performance-tests can not find rome:rome:1.0 in the developer repository. I checked the repository and indeed this directory does not exist https://repository.jboss.org/nexus/content/groups/developer/rome/rome The directory above it, https://repository.jboss.org/nexus/content/groups/developer/rome does exist and is dated Sun Mar 24 18:33:22 EDT 2019. Nexus appear to have failed with this upload. In order to run the tests I downloaded the jar from maven central and put it in my local repo. In looking for this jar file I found rome:rome:1.0 is very old. The last release was 2010-05-10. There is a newer version here, https://mvnrepository.com/artifact/com.rometools/rome <dependency> <groupId>com.rometools</groupId> <artifactId>rome</artifactId> <version>1.12.0</version> </dependency> I have not been able to determine what is depending on this archive. mvn dependency:tree does not provided helpful information. Adding the dependency above does not override the old version and use the newer one. I don't know who is responsible for fixing the developer nexus https://repository.jboss.org/nexus/content/groups/developer/rome/rome Should a jira be created to upgrade rome to a more current version? > jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec > ---------------------------------------------------------------------------------------- > > Key: JBWS-4154 > URL: https://issues.jboss.org/browse/JBWS-4154 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: r searls > Priority: Major > Fix For: jbossws-cxf-5.3.0.Final > > > dependency:tree goal output shows that jbossws-cxf-client (and transitively other modules too) depends on two versions of JBoss JAX-WS API: > org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile > org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.3_spec:jar:1.0.0.Final:compile > The former is brought in by: > {code:java} > +- org.jboss.ws.cxf:jbossws-cxf-transports-undertow:jar:5.2.5-SNAPSHOT:compile > | \- org.jboss.ws.projects:jaxws-undertow-httpspi:jar:1.0.1.Final:compile > | +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile > {code} > I guess we should stick to the newer one which would mean add some dependency exclude or update jaxws-undertow-httpspi to new API version stream (I vote for this) > Whole dependency tree at https://github.com/jbliznak/jbws-dependency-trees/blob/jdk11-after/jbossw... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4133) Deal with java.security.acl classes being removed in Java 12

by r searls (Jira)

[ https://issues.jboss.org/browse/JBWS-4133?page=com.atlassian.jira.plugin.... ] r searls commented on JBWS-4133: -------------------------------- There are a handful of classes that import one or both of following security APIs deprecated in jdk-9. java.security.acl.Group java.security.Principal Both of these classes are used as building blocks (i.e input and output parameters) to apache classes which jbossws-cxf uses. org.apache.cxf.security.SecurityContext org.apache.cxf.common.security.SimplePrincipal org.apache.cxf.interceptor.security.DefaultSecurityContext Because of this we need to wait until cxf changes their classes before we make corresponding changes to jbossws-cxf. Sean Mullan states in https://issues.apache.org/jira/browse/CXF-7815 in a 7/Nov18 comment ... they are deferring removal of java.security.acl APIs to jdk-13 cxf-3.3.1 has no changes on this issue. We should wait on CXF. > Deal with java.security.acl classes being removed in Java 12 > ------------------------------------------------------------ > > Key: JBWS-4133 > URL: https://issues.jboss.org/browse/JBWS-4133 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: r searls > Priority: Major > Fix For: jbossws-cxf-5.3.0.Final > > > See https://issues.apache.org/jira/browse/CXF-7815 / https://bugs.openjdk.java.net/browse/JDK-8191138 . > We also make direct use of Group in our SubjectCreatingInterceptors, which are extensions of CXF ones. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4154) jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec

by r searls (Jira)

[ https://issues.jboss.org/browse/JBWS-4154?page=com.atlassian.jira.plugin.... ] r searls commented on JBWS-4154: -------------------------------- Also compiling project jaxws-undertow-httpspi with jdk-10 there is an error from maven-enforcer. Want me to file a jira for that as well? > jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec > ---------------------------------------------------------------------------------------- > > Key: JBWS-4154 > URL: https://issues.jboss.org/browse/JBWS-4154 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: r searls > Priority: Major > Fix For: jbossws-cxf-5.3.0.Final > > > dependency:tree goal output shows that jbossws-cxf-client (and transitively other modules too) depends on two versions of JBoss JAX-WS API: > org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile > org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.3_spec:jar:1.0.0.Final:compile > The former is brought in by: > {code:java} > +- org.jboss.ws.cxf:jbossws-cxf-transports-undertow:jar:5.2.5-SNAPSHOT:compile > | \- org.jboss.ws.projects:jaxws-undertow-httpspi:jar:1.0.1.Final:compile > | +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile > {code} > I guess we should stick to the newer one which would mean add some dependency exclude or update jaxws-undertow-httpspi to new API version stream (I vote for this) > Whole dependency tree at https://github.com/jbliznak/jbws-dependency-trees/blob/jdk11-after/jbossw... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4154) jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec

by r searls (Jira)

[ https://issues.jboss.org/browse/JBWS-4154?page=com.atlassian.jira.plugin.... ] r searls commented on JBWS-4154: -------------------------------- Do you want me to file a jira to update jaxws-undertow-httpspi to upgrade to jboss-jaxws-api_2.3_spec? > jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec > ---------------------------------------------------------------------------------------- > > Key: JBWS-4154 > URL: https://issues.jboss.org/browse/JBWS-4154 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: r searls > Priority: Major > Fix For: jbossws-cxf-5.3.0.Final > > > dependency:tree goal output shows that jbossws-cxf-client (and transitively other modules too) depends on two versions of JBoss JAX-WS API: > org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile > org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.3_spec:jar:1.0.0.Final:compile > The former is brought in by: > {code:java} > +- org.jboss.ws.cxf:jbossws-cxf-transports-undertow:jar:5.2.5-SNAPSHOT:compile > | \- org.jboss.ws.projects:jaxws-undertow-httpspi:jar:1.0.1.Final:compile > | +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile > {code} > I guess we should stick to the newer one which would mean add some dependency exclude or update jaxws-undertow-httpspi to new API version stream (I vote for this) > Whole dependency tree at https://github.com/jbliznak/jbws-dependency-trees/blob/jdk11-after/jbossw... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 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 April 2019