January 2017 - jbossws-issues - Jboss List Archives

[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

[JBoss JIRA] (JBWS-4044) Upgrade to Apache Santuario 2.0.8

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4044?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4044: ---------------------------------- Issue Type: Component Upgrade (was: Task) > Upgrade to Apache Santuario 2.0.8 > --------------------------------- > > Key: JBWS-4044 > URL: https://issues.jboss.org/browse/JBWS-4044 > Project: JBoss Web Services > Issue Type: Component Upgrade > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.7.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4051) Revisit details on available cryptography for tests

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-4051?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4051: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/21 > Revisit details on available cryptography for tests > --------------------------------------------------- > > Key: JBWS-4051 > URL: https://issues.jboss.org/browse/JBWS-4051 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.6.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Optional > > Currently there are two tests classes that informs user about actual BouncyCastle and unlimited stregth cryptography availability: > org.jboss.wsf.test.CryptoCheckMain that informs about BC availibility during execution of test-utils module > org.jboss.wsf.test.CryptoHelper that provides hints for exceptions in security related tests. > But both only recognize BouncyCastleProvider installed within security providers while JBossWS 5+ can also load BC provider from classpath. Thus the current mechanism can wrap actual exception in false warning on missing BC. > The proposal is to move printing info from test-utils to testsuite module to be printed where it actually matters. > The second proposal is to merge both classes and also detect the BC on test classpath. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4051) Revisit details on available cryptography for tests

by Jan Blizňák (JIRA)

Jan Blizňák created JBWS-4051: --------------------------------- Summary: Revisit details on available cryptography for tests Key: JBWS-4051 URL: https://issues.jboss.org/browse/JBWS-4051 Project: JBoss Web Services Issue Type: Enhancement Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.6.Final Reporter: Jan Blizňák Assignee: Jan Blizňák Priority: Optional Currently there are two tests classes that informs user about actual BouncyCastle and unlimited stregth cryptography availability: org.jboss.wsf.test.CryptoCheckMain that informs about BC availibility during execution of test-utils module org.jboss.wsf.test.CryptoHelper that provides hints for exceptions in security related tests. But both only recognize BouncyCastleProvider installed within security providers while JBossWS 5+ can also load BC provider from classpath. Thus the current mechanism can wrap actual exception in false warning on missing BC. The proposal is to move printing info from test-utils to testsuite module to be printed where it actually matters. The second proposal is to merge both classes and also detect the BC on test classpath. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4050) JBWS1178TestCase issues

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-4050?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4050: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/20 > JBWS1178TestCase issues > ----------------------- > > Key: JBWS-4050 > URL: https://issues.jboss.org/browse/JBWS-4050 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.6.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > > During migration to Arquillian-based testsuite back in 4.x --> 5.x move, there was made a mistake in JBWS1178TestCase#testHostName test, effectively leaving both tests of the class the same. > The tests also need some sanitazing of IPv6 IP address formats as these might be different for the same address which leads to false-negatives fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4050) JBWS1178TestCase issues

by Jan Blizňák (JIRA)

Jan Blizňák created JBWS-4050: --------------------------------- Summary: JBWS1178TestCase issues Key: JBWS-4050 URL: https://issues.jboss.org/browse/JBWS-4050 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.6.Final Reporter: Jan Blizňák Assignee: Jan Blizňák During migration to Arquillian-based testsuite back in 4.x --> 5.x move, there was made a mistake in JBWS1178TestCase#testHostName test, effectively leaving both tests of the class the same. The tests also need some sanitazing of IPv6 IP address formats as these might be different for the same address which leads to false-negatives fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4049) Upgrade to Apache CXF 3.1.9

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-4049: ------------------------------------- Summary: Upgrade to Apache CXF 3.1.9 Key: JBWS-4049 URL: https://issues.jboss.org/browse/JBWS-4049 Project: JBoss Web Services Issue Type: Component Upgrade Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.1.7.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3873) Web Services can't inherit a JDK8 default method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3873?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3873: ----------------------------------------------- Peter Mackay <pmackay(a)redhat.com> changed the Status of [bug 1196686|https://bugzilla.redhat.com/show_bug.cgi?id=1196686] from ON_QA to VERIFIED > Web Services can't inherit a JDK8 default method > ------------------------------------------------ > > Key: JBWS-3873 > URL: https://issues.jboss.org/browse/JBWS-3873 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta3 > Environment: JDK8 > Reporter: Jan Blizňák > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0.1.Final, jbossws-cxf-5.1.0.Beta1 > > Attachments: jdk8-ws-defaultmethod.zip > > > Having simple SEI and POJO webservice with JDK8 feature - default method for interface: > {code} > @WebService > public interface GreeterSEI { > default public String sayHello() { > return "Hello, Default"; > } > } > > //---------------------------------------------------------- > > @WebService > public class GreeterImpl implements GreeterSEI {} > {code} > When you try to execute sayHello method: > {code} > Service greeterService = Service.create(...); > GreeterSEI g = greeterService.getPort(GreeterSEI.class); > > Assert.assertEquals("JBoss", greeter.sayHello()); > {code} > You will get a message-less IllegalStateException on server. > Expected results: > no exception, default implementation of method is invoked. > Or if this is considered unsupported usage, the exception should be more descriptive (ie.: "Method xx not found on implementation class") -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3945) Set property that causes 400 error message to be returned by apache CXF.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3945?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3945: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1182919|https://bugzilla.redhat.com/show_bug.cgi?id=1182919] from VERIFIED to CLOSED > Set property that causes 400 error message to be returned by apache CXF. > ------------------------------------------------------------------------ > > Key: JBWS-3945 > URL: https://issues.jboss.org/browse/JBWS-3945 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.0.Beta1 > Reporter: R Searls > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-5.1.1.Final > > > Change ./modules/client/src/main/java/org/jboss/wsf/stack/cxf/saaj/SOAPConnectionImpl.java -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3863) @MTOM.enabled is not honored

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3863?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3863: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1178234|https://bugzilla.redhat.com/show_bug.cgi?id=1178234] from VERIFIED to CLOSED > @MTOM.enabled is not honored > ---------------------------- > > Key: JBWS-3863 > URL: https://issues.jboss.org/browse/JBWS-3863 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3.1 > Reporter: Kyle Lape > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.0.Beta3 > > Attachments: jbws3863.diff > > > If you put {{@MTOM(enabled=false)}} on an endpoint, it will still send responses as if MTOM is enabled. If you remove the annotation altogether, the endpoint will end up inlining the content as you'd expect. This does not occur if you run CXF standalone -- only when using the JBossWS integration layer in JBoss. -- 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