April 2019 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4064) Non-URL encoded Content-Id href does not seem be serialized by CXF's AttachmentSerializer

by Viral Gohel (Jira)

[ https://issues.jboss.org/browse/JBWS-4064?page=com.atlassian.jira.plugin.... ] Viral Gohel commented on JBWS-4064: ----------------------------------- Thanks [~pjurak]. I will test this and let you know. > Non-URL encoded Content-Id href does not seem be serialized by CXF's AttachmentSerializer > ----------------------------------------------------------------------------------------- > > Key: JBWS-4064 > URL: https://issues.jboss.org/browse/JBWS-4064 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.8.Final > Reporter: Viral Gohel > Assignee: Petr Jurak > Priority: Major > Fix For: jbossws-cxf-5.3.0.Final > > Attachments: mtomExample.war, mtomLog.txt > > > Check issue, https://issues.apache.org/jira/browse/CXF-7317 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4064) Non-URL encoded Content-Id href does not seem be serialized by CXF's AttachmentSerializer

by Petr Jurak (Jira)

[ https://issues.jboss.org/browse/JBWS-4064?page=com.atlassian.jira.plugin.... ] Petr Jurak updated JBWS-4064: ----------------------------- Attachment: mtomLog.txt > Non-URL encoded Content-Id href does not seem be serialized by CXF's AttachmentSerializer > ----------------------------------------------------------------------------------------- > > Key: JBWS-4064 > URL: https://issues.jboss.org/browse/JBWS-4064 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.8.Final > Reporter: Viral Gohel > Assignee: Petr Jurak > Priority: Major > Fix For: jbossws-cxf-5.3.0.Final > > Attachments: mtomExample.war, mtomLog.txt > > > Check issue, https://issues.apache.org/jira/browse/CXF-7317 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4156) Get rid of duplicated executions of maven plugins

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4156?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on JBWS-4156: ----------------------------------- This is waiting for the new jbossws-parent release to be consumed in jbossws-cxf. > Get rid of duplicated executions of maven plugins > ------------------------------------------------- > > Key: JBWS-4156 > URL: https://issues.jboss.org/browse/JBWS-4156 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Minor > Fix For: jbossws-cxf-5.3.0.Final > > > There are some plugins' executions executed more times during the build. > More specifically this issue appears for maven-jar-plugin and exec-maven-plugin: > {code:java} > [INFO] ------------------------------------------------------------------------ > [INFO] Building JBoss Web Services - Stack CXF Testsuite 5.2.5-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-antrun-plugin:1.8:run (validate-jboss-home) @ jbossws-cxf-testsuite --- > [INFO] Executing tasks > main: > [echo] > [echo] profile=wildfly1400 > [echo] jboss.home=/home/travis/build/jbossws/jbossws-cxf/modules/testsuite/target/test-server/jbossws-cxf-dist-5.2.5-SNAPSHOT/wildfly-14.0.0.Final > [echo] > [INFO] Executed tasks > [INFO] > [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-java-version) @ jbossws-cxf-testsuite --- > [INFO] > [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-maven-version) @ jbossws-cxf-testsuite --- > [INFO] > [INFO] --- build-helper-maven-plugin:1.12:add-test-source (add-source) @ jbossws-cxf-testsuite --- > [INFO] Test Source directory: /home/travis/build/jbossws/jbossws-cxf/modules/testsuite/target/wsconsume/java added. > [INFO] > [INFO] >>> maven-source-plugin:3.0.1:jar (attach-sources) > generate-sources @ jbossws-cxf-testsuite >>> > [INFO] > [INFO] --- maven-antrun-plugin:1.8:run (validate-jboss-home) @ jbossws-cxf-testsuite --- > [INFO] Executing tasks > main: > [echo] > [echo] profile=wildfly1400 > [echo] jboss.home=/home/travis/build/jbossws/jbossws-cxf/modules/testsuite/target/test-server/jbossws-cxf-dist-5.2.5-SNAPSHOT/wildfly-14.0.0.Final > [echo] > [INFO] Executed tasks > [INFO] > [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-java-version) @ jbossws-cxf-testsuite --- > [INFO] > [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-maven-version) @ jbossws-cxf-testsuite --- > [INFO] > [INFO] --- build-helper-maven-plugin:1.12:add-test-source (add-source) @ jbossws-cxf-testsuite --- > [INFO] Test Source directory: /home/travis/build/jbossws/jbossws-cxf/modules/testsuite/target/wsconsume/java added. > [INFO] > [INFO] <<< maven-source-plugin:3.0.1:jar (attach-sources) < generate-sources @ jbossws-cxf-testsuite <<< > [INFO] > [INFO] > [INFO] --- maven-source-plugin:3.0.1:jar (attach-sources) @ jbossws-cxf-testsuite --- > [INFO] > [INFO] --- maven-javadoc-plugin:3.0.1:jar (default) @ jbossws-cxf-testsuite --- > [INFO] Skipping javadoc generation > [INFO] > [INFO] --- maven-dependency-plugin:3.1.1:unpack (unpack) @ jbossws-cxf-testsuite --- > [INFO] Configured Artifact: org.jboss.ws.cxf:jbossws-cxf-dist:wildfly1400:5.2.5-SNAPSHOT:zip > [INFO] Unpacking /home/travis/build/jbossws/jbossws-cxf/modules/dist/target/jbossws-cxf-dist-5.2.5-SNAPSHOT-wildfly1400.zip to /home/travis/build/jbossws/jbossws-cxf/modules/testsuite/target/test-server with includes "" and excludes "" > [INFO] > [INFO] >>> exec-maven-plugin:1.2.1:java (check-bc-and-unlimited-crypto) > validate @ jbossws-cxf-testsuite >>> > [INFO] > [INFO] --- maven-antrun-plugin:1.8:run (validate-jboss-home) @ jbossws-cxf-testsuite --- > [INFO] Executing tasks > main: > [echo] > [echo] profile=wildfly1400 > [echo] jboss.home=/home/travis/build/jbossws/jbossws-cxf/modules/testsuite/target/test-server/jbossws-cxf-dist-5.2.5-SNAPSHOT/wildfly-14.0.0.Final > [echo] > [INFO] Executed tasks > [INFO] > [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-java-version) @ jbossws-cxf-testsuite --- > [INFO] > [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-maven-version) @ jbossws-cxf-testsuite --- > [INFO] > [INFO] <<< exec-maven-plugin:1.2.1:java (check-bc-and-unlimited-crypto) < validate @ jbossws-cxf-testsuite <<< > [INFO] > [INFO] > [INFO] --- exec-maven-plugin:1.2.1:java (check-bc-and-unlimited-crypto) @ jbossws-cxf-testsuite --- > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX > JCE unlimited strength cryptography: AVAILABLE > Bouncy Castle JCE Provider: AVAILABLE - ON CLASSPATH (ver: 1.6, file:/home/travis/.m2/repository/org/bouncycastle/bcprov-jdk15on/1.60/bcprov-jdk15on-1.60.jar) > XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX > [INFO] > [INFO] --- maven-surefire-plugin:2.22.0:test (integration-tests) @ jbossws-cxf-testsuite --- > [INFO] No tests to run. > [INFO] > [INFO] --- maven-surefire-plugin:2.22.0:test (forked-integration-tests) @ jbossws-cxf-testsuite --- > [INFO] No tests to run. > [INFO] > {code} > The fix for source plugin is to use it properly, ie. use {{jar-no-fork}} goal instead of {{jar}}. > For the exec plugin, this was fixed ages ago in version 1.3 so we just need to uprade. -- 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 Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4133?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-4133: ------------------------------ [~rsearls] Can you please check if we need to something in jbossws besides the cxf 3.3.1 upgrade ? > 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-4133) Deal with java.security.acl classes being removed in Java 12

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4133?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-4133: ------------------------- Assignee: r searls > 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 Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4154?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-4154: ------------------------- Assignee: r searls (was: Jim Ma) > 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-4148) Upgrade to Apache CXF 3.3.1

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4148?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-4148: ------------------------- Summary: Upgrade to Apache CXF 3.3.1 (was: Upgrade to Apache CXF 3.2.7) > Upgrade to Apache CXF 3.3.1 > --------------------------- > > Key: JBWS-4148 > URL: https://issues.jboss.org/browse/JBWS-4148 > Project: JBoss Web Services > Issue Type: Component Upgrade > Components: jbossws-cxf > Reporter: Alessio Soldano > Priority: Major > Fix For: jbossws-cxf-5.3.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

[JBoss JIRA] (JBWS-4165) jaxws-tools-maven-plugin forked wsconsume requires java on Windows PATH

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4165?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-4165: ------------------------- Fix Version/s: jbossws-jaxws-tools-maven.plugin-1.2.3.Final > jaxws-tools-maven-plugin forked wsconsume requires java on Windows PATH > ----------------------------------------------------------------------- > > Key: JBWS-4165 > URL: https://issues.jboss.org/browse/JBWS-4165 > Project: JBoss Web Services > Issue Type: Bug > Components: jaxws-tools-maven-plugin > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: jbossws-jaxws-tools-maven.plugin-1.2.3.Final > > > When running on forked mode, the plugin looks for the Java executable at path JAVA_HOME/bin/java, but on Windows the file name is java.exe. Ultimately this means that on Windows, the plugin forked mode (explicit or due to JDK version 1.8+) requires that the java executable is on PATH environment. -- 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