July 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3931) Upgrade to Apache CXF 3.1.x

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3931: ------------------------------------- Summary: Upgrade to Apache CXF 3.1.x Key: JBWS-3931 URL: https://issues.jboss.org/browse/JBWS-3931 Project: JBoss Web Services Issue Type: Feature Request Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-5.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3930) Upgrade to Apache CXF 3.0.6

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3930?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3930 at 7/6/15 5:57 PM: --------------------------------------------------------------- Linked to SANTUARIO-420 as that is required for GCM functionalities when running on JDK 1.8 (and without BouncyCastle installed on the JDK) was (Author: asoldano): Linked to SANTUARIO-420 as that is required for GCM functionalities when running on JDK 1.8 > Upgrade to Apache CXF 3.0.6 > --------------------------- > > Key: JBWS-3930 > URL: https://issues.jboss.org/browse/JBWS-3930 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.1 > > > Upgrade to Apache CXF 3.0.6. This includes upgrading WSS4J and Santuario to 2.0.5 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3930) Upgrade to Apache CXF 3.0.6

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3930?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3930: --------------------------------------- Linked to SANTUARIO-420 as that is required for GCM functionalities when running on JDK 1.8 > Upgrade to Apache CXF 3.0.6 > --------------------------- > > Key: JBWS-3930 > URL: https://issues.jboss.org/browse/JBWS-3930 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.1 > > > Upgrade to Apache CXF 3.0.6. This includes upgrading WSS4J and Santuario to 2.0.5 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3930) Upgrade to Apache CXF 3.0.6

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3930: ------------------------------------- Summary: Upgrade to Apache CXF 3.0.6 Key: JBWS-3930 URL: https://issues.jboss.org/browse/JBWS-3930 Project: JBoss Web Services Issue Type: Feature Request Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0.1 Upgrade to Apache CXF 3.0.6. This includes upgrading WSS4J and Santuario to 2.0.5 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3929) Remove support for JDK 1.7

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3929: ------------------------------------- Summary: Remove support for JDK 1.7 Key: JBWS-3929 URL: https://issues.jboss.org/browse/JBWS-3929 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-5.1 With JBossWS 5.1.x series we should likely drop JDK 1.7 and require 1.8. By doing that we can also get rid of all -XX:MaxPermSize options in the various config files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3928) jbws-testsuite-jms.groovy script breaks build with WFLY 10

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3928: ------------------------------------- Summary: jbws-testsuite-jms.groovy script breaks build with WFLY 10 Key: JBWS-3928 URL: https://issues.jboss.org/browse/JBWS-3928 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.1 WildFly 10 has moved from HornetQ to Apache Active Artemis, hence our current script can not find the expected elements to update in the model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3913) Create WildFly 9.0 ASIL

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3913?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3913: ---------------------------------- Assignee: Alessio Soldano > Create WildFly 9.0 ASIL > ----------------------- > > Key: JBWS-3913 > URL: https://issues.jboss.org/browse/JBWS-3913 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1 > > > With current WildFly master development moving to version 10, we'll eventually need an integration layer for 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3927) Remove java.endorsed.dirs requirement for properly setup clients

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3927?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3927: ---------------------------------- Description: Starting from JDK 1.8_40, the Java Endorsed Standards Override Mechanism is deprecated https://docs.oracle.com/javase/8/docs/technotes/guides/standards/ , basically because with the Jigsaw changes coming in JDK 9 that will not be supported / usable anymore. JBossWS currently relies on the afore mentioned endorsing mechanism for: * ensuring the JBossWS implementation of JAX-WS SPI Provider is used (instead of the Apache CXF or JDK JAXWS RI ones), regardless of how the classpath is defined; * ensuring the JBossWS implementation of Apache CXF BusFactory is used (instead of the vanilla Apache CXF one), regardless of how the classpath is defined. So, we need to get rid of the endorsing mechanism, at least for properly configured client classpaths in which the jbossws-cxf-factories jar is always included and comes before any Apache CXF jar. This implies carefully defining the jbossws-cxf poms and possibly restricting the supported JDKs from now on (depending on the JAX-WS api version they come with). The changes here do not ensure users will always automatically use the correct integration when not setting endorsing, basically because it will be up to them to e.g. avoid declaring Apache CXF dependencies before the JBossWS ones. We might put in place some runtime checks on the classpath or additional alternative mechanims as part of a different and future effort (when JDK9 will be supported). was: Starting from JDK 1.8_40, the Java Endorsed Standards Override Mechanism is deprecated https://docs.oracle.com/javase/8/docs/technotes/guides/standards/ , basically because with the Jigsaw changes coming in JDK 9 that will not be supported / usable anymore. JBossWS currently relies on the afore mentioned endorsing mechanism for: * ensuring the JBossWS implementation of JAX-WS SPI Provider is used (instead of the Apache CXF or JDK JAXWS RI ones), regardless of how the classpath is defined; * ensuring the JBossWS implementation of Apache CXF BusFactory is used (instead of the vanilla Apache CXF one), regardless of how the classpath is defined. So, we need to get rid of the endorsing mechanism, at least for properly configured client classpaths in which the jbossws-cxf-factories jar is always included and comes before any Apache CXF jar. This implies carefully defining the jbossws-cxf poms. The changes here do not ensure users will always automatically use the correct integration when not setting endorsing, basically because it will be up to them to e.g. avoid declaring Apache CXF dependencies before the JBossWS ones. We might put in place some runtime checks on the classpath or additional alternative mechanims as part of a different and future effort (when JDK9 will be supported). > Remove java.endorsed.dirs requirement for properly setup clients > ---------------------------------------------------------------- > > Key: JBWS-3927 > URL: https://issues.jboss.org/browse/JBWS-3927 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1 > > > Starting from JDK 1.8_40, the Java Endorsed Standards Override Mechanism is deprecated https://docs.oracle.com/javase/8/docs/technotes/guides/standards/ , basically because with the Jigsaw changes coming in JDK 9 that will not be supported / usable anymore. > JBossWS currently relies on the afore mentioned endorsing mechanism for: > * ensuring the JBossWS implementation of JAX-WS SPI Provider is used (instead of the Apache CXF or JDK JAXWS RI ones), regardless of how the classpath is defined; > * ensuring the JBossWS implementation of Apache CXF BusFactory is used (instead of the vanilla Apache CXF one), regardless of how the classpath is defined. > So, we need to get rid of the endorsing mechanism, at least for properly configured client classpaths in which the jbossws-cxf-factories jar is always included and comes before any Apache CXF jar. > This implies carefully defining the jbossws-cxf poms and possibly restricting the supported JDKs from now on (depending on the JAX-WS api version they come with). > The changes here do not ensure users will always automatically use the correct integration when not setting endorsing, basically because it will be up to them to e.g. avoid declaring Apache CXF dependencies before the JBossWS ones. We might put in place some runtime checks on the classpath or additional alternative mechanims as part of a different and future effort (when JDK9 will be supported). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3927) Remove java.endorsed.dirs requirement for properly setup clients

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3927: ------------------------------------- Summary: Remove java.endorsed.dirs requirement for properly setup clients Key: JBWS-3927 URL: https://issues.jboss.org/browse/JBWS-3927 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.1 Starting from JDK 1.8_40, the Java Endorsed Standards Override Mechanism is deprecated https://docs.oracle.com/javase/8/docs/technotes/guides/standards/ , basically because with the Jigsaw changes coming in JDK 9 that will not be supported / usable anymore. JBossWS currently relies on the afore mentioned endorsing mechanism for: * ensuring the JBossWS implementation of JAX-WS SPI Provider is used (instead of the Apache CXF or JDK JAXWS RI ones), regardless of how the classpath is defined; * ensuring the JBossWS implementation of Apache CXF BusFactory is used (instead of the vanilla Apache CXF one), regardless of how the classpath is defined. So, we need to get rid of the endorsing mechanism, at least for properly configured client classpaths in which the jbossws-cxf-factories jar is always included and comes before any Apache CXF jar. This implies carefully defining the jbossws-cxf poms. The changes here do not ensure users will always automatically use the correct integration when not setting endorsing, basically because it will be up to them to e.g. avoid declaring Apache CXF dependencies before the JBossWS ones. We might put in place some runtime checks on the classpath or additional alternative mechanims as part of a different and future effort (when JDK9 will be supported). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3926) EndorseTestCase#testClientSide() is not run

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3926: ------------------------------------- Summary: EndorseTestCase#testClientSide() is not run Key: JBWS-3926 URL: https://issues.jboss.org/browse/JBWS-3926 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Priority: Minor Fix For: jbossws-cxf-5.1 When performing the migration of the testsuite to Arquillian, the EndorseTestCase has not been properly modified, hence the testClientSide() method is erroneously not run. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 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 July 2015