May 2018 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4121) testsuite changes to refect wfly script changes for -secmgr

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-4121?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-4121: -------------------------------- Affected tests. + WSConsumeScriptTestCase + WSProvideScriptTestCase + JBWS2528TestCase ; wsprovide + JBWS2591TestCase ; wsconsume + JBWS2529TestCase ; wsprovide + JBWS2593TestCase ; wsconsume + ServiceRefTestCase ; appclient + AppclientHelper ; appclient + WebServiceRefTestCase ; appclient + JBWS1666TestCase + ClientBusStrategyTestCase > testsuite changes to refect wfly script changes for -secmgr > ----------------------------------------------------------- > > Key: JBWS-4121 > URL: https://issues.jboss.org/browse/JBWS-4121 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.2.Final > Reporter: R Searls > Assignee: R Searls > > Change tests for wildlfy scripts appclient, wsconsume, wsprovide to reflect handling changes to support -secmgr flag. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4121) testsuite changes to refect wfly script changes for -secmgr

by R Searls (JIRA)

R Searls created JBWS-4121: ------------------------------ Summary: testsuite changes to refect wfly script changes for -secmgr Key: JBWS-4121 URL: https://issues.jboss.org/browse/JBWS-4121 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-5.2.2.Final Reporter: R Searls Assignee: R Searls Change tests for wildlfy scripts appclient, wsconsume, wsprovide to reflect handling changes to support -secmgr flag. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4120) SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2)

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-4120?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda updated JBWS-4120: ------------------------------------ Affects Version/s: jbossws-cxf-5.2.0.Final > SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) > ------------------------------------------------------------------------------------- > > Key: JBWS-4120 > URL: https://issues.jboss.org/browse/JBWS-4120 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.2.0.Final > Reporter: Rostislav Svoboda > Priority: Critical > > SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) > This is working with WildFly 11 / JBossWS 5.1.9.Final (Apache CXF 3.1.12) > {code} > wildfly-11.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty > wildfly-12.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty > {code} > Seems that logging feature is not activated, I tried also {{org.apache.cxf.logging.enabled=true}}. > It can be related to https://github.com/apache/cxf/commit/54e7c58d5449d5f91879674598fe1b1ee339... changes where logging was refactored and new LoggingBusLifecycleListener was introduced. > I used https://github.com/wildfly/quickstart/tree/master/helloworld-ws app ++ SoapUI for quick check. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4120) SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2)

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-4120?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda updated JBWS-4120: ------------------------------------ Description: SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) This is working with WildFly 11 / JBossWS 5.1.9.Final (Apache CXF 3.1.12) {code} wildfly-11.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty wildfly-12.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty {code} Seems that logging feature is not activated, I tried also {{org.apache.cxf.logging.enabled=true}}. It can be related to https://github.com/apache/cxf/commit/54e7c58d5449d5f91879674598fe1b1ee339... changes where logging was refactored and new LoggingBusLifecycleListener was introduced. I used https://github.com/wildfly/quickstart/tree/master/helloworld-ws app ++ SoapUI for quick check. was: SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) This is working with WildFly 11 / JBossWS 5.1.9.Final (Apache CXF 3.1.12) {code} wildfly-11.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty wildfly-12.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty {code} Seems that logging feature is not activated, I tried also {{org.apache.cxf.logging.enabled=true}. It can be related to https://github.com/apache/cxf/commit/54e7c58d5449d5f91879674598fe1b1ee339... changes where logging was refactored and new LoggingBusLifecycleListener was introduced. I used https://github.com/wildfly/quickstart/tree/master/helloworld-ws app ++ SoapUI for quick check. > SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) > ------------------------------------------------------------------------------------- > > Key: JBWS-4120 > URL: https://issues.jboss.org/browse/JBWS-4120 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.2.0.Final > Reporter: Rostislav Svoboda > Priority: Critical > > SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) > This is working with WildFly 11 / JBossWS 5.1.9.Final (Apache CXF 3.1.12) > {code} > wildfly-11.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty > wildfly-12.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty > {code} > Seems that logging feature is not activated, I tried also {{org.apache.cxf.logging.enabled=true}}. > It can be related to https://github.com/apache/cxf/commit/54e7c58d5449d5f91879674598fe1b1ee339... changes where logging was refactored and new LoggingBusLifecycleListener was introduced. > I used https://github.com/wildfly/quickstart/tree/master/helloworld-ws app ++ SoapUI for quick check. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4120) SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2)

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/JBWS-4120?page=com.atlassian.jira.plugin.... ] Rostislav Svoboda updated JBWS-4120: ------------------------------------ Description: SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) This is working with WildFly 11 / JBossWS 5.1.9.Final (Apache CXF 3.1.12) {code} wildfly-11.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty wildfly-12.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty {code} Seems that logging feature is not activated, I tried also {{org.apache.cxf.logging.enabled=true}. It can be related to https://github.com/apache/cxf/commit/54e7c58d5449d5f91879674598fe1b1ee339... changes where logging was refactored and new LoggingBusLifecycleListener was introduced. I used https://github.com/wildfly/quickstart/tree/master/helloworld-ws app ++ SoapUI for quick check. was: SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) This is working with WildFly 11 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) {code} wildfly-11.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty wildfly-12.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty {code} Seems that logging feature is not activated, I tried also {{org.apache.cxf.logging.enabled=true}. It can be related to https://github.com/apache/cxf/commit/54e7c58d5449d5f91879674598fe1b1ee339... changes where logging was refactored and new LoggingBusLifecycleListener was introduced. I used https://github.com/wildfly/quickstart/tree/master/helloworld-ws app ++ SoapUI for quick check. > SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) > ------------------------------------------------------------------------------------- > > Key: JBWS-4120 > URL: https://issues.jboss.org/browse/JBWS-4120 > Project: JBoss Web Services > Issue Type: Bug > Reporter: Rostislav Svoboda > Priority: Critical > > SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) > This is working with WildFly 11 / JBossWS 5.1.9.Final (Apache CXF 3.1.12) > {code} > wildfly-11.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty > wildfly-12.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty > {code} > Seems that logging feature is not activated, I tried also {{org.apache.cxf.logging.enabled=true}. > It can be related to https://github.com/apache/cxf/commit/54e7c58d5449d5f91879674598fe1b1ee339... changes where logging was refactored and new LoggingBusLifecycleListener was introduced. > I used https://github.com/wildfly/quickstart/tree/master/helloworld-ws app ++ SoapUI for quick check. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4120) SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2)

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created JBWS-4120: --------------------------------------- Summary: SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) Key: JBWS-4120 URL: https://issues.jboss.org/browse/JBWS-4120 Project: JBoss Web Services Issue Type: Bug Reporter: Rostislav Svoboda Priority: Critical SOAP logging stopped working with WildFly 12 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) This is working with WildFly 11 / JBossWS 5.2.0.Final (Apache CXF 3.2.2) {code} wildfly-11.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty wildfly-12.0.0.Final/bin/standalone.sh -Dorg.apache.cxf.logging.enabled=pretty {code} Seems that logging feature is not activated, I tried also {{org.apache.cxf.logging.enabled=true}. It can be related to https://github.com/apache/cxf/commit/54e7c58d5449d5f91879674598fe1b1ee339... changes where logging was refactored and new LoggingBusLifecycleListener was introduced. I used https://github.com/wildfly/quickstart/tree/master/helloworld-ws app ++ SoapUI for quick check. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4093) Upgrade to Apache CXF 3.2.2

by Alessio Soldano (JIRA)

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

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4099) JDK10 support

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4099?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4099: ---------------------------------- Issue Type: Task (was: Feature Request) > JDK10 support > ------------- > > Key: JBWS-4099 > URL: https://issues.jboss.org/browse/JBWS-4099 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.1.Final > > > With JDK10 release coming within weeks we should enable JBWS to build and test also on this JDK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4101) Wsprovide tool ends with java.security.AccessControlException

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4101?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4101: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.1.Final (was: jbossws-cxf-5.2.2.Final) > Wsprovide tool ends with java.security.AccessControlException > ------------------------------------------------------------- > > Key: JBWS-4101 > URL: https://issues.jboss.org/browse/JBWS-4101 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, tools-jaxws > Affects Versions: jbossws-cxf-5.2.1.Final > Reporter: R Searls > Assignee: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.2.1.Final > > > There are changes to the security manager in jboss-modules in wfly 12. This > has broken the default behavior of wfly's wsprovide script. This is expected > to be resolved in future wfly 12 releases. > Continued follow up is needed. > https://issues.jboss.org/browse/JBWS-4100 and https://issues.jboss.org/browse/WFLY-9868 > are changes that added in support of future work. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4087) SOAP address rewrite for wsdl-uri-scheme=https for nested XML schema documents (XSD) referenced by the WSDL behind reverse proxy

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4087?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4087: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.2.Final (was: jbossws-cxf-5.2.1.Final) > SOAP address rewrite for wsdl-uri-scheme=https for nested XML schema documents (XSD) referenced by the WSDL behind reverse proxy > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBWS-4087 > URL: https://issues.jboss.org/browse/JBWS-4087 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.5.Final > Environment: Wildfly 10 > JBossWS 5.1.5-Final > Reporter: Nico Schlebusch > Labels: JBossWS > Fix For: jbossws-cxf-5.2.2.Final > > > We have Wildfly 10 configured behind NGINX as a reverse proxy for handling the SSL requirements of the web service. Wildfly serves everything as plain HTTP and NGINX handles the HTTPS side of the request. The webservices subsystem is configured to rewrite the uri using https schema. The XSD schema location referenced inside the WSDL is rewritten to use https. However, any other XSD's scheme location that is referenced by the first XSD is not changed to use https. > The URI rewriting for the SOAP address and the schema location of the XSD included in the WSDL works correctly. > {{<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" > xmlns:tns="http://example.systems/webservices/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" > xmlns:ns1="http://example.co.za/claim/zmf" attributeFormDefault="unqualified" elementFormDefault="unqualified" > targetNamespace="http://example.systems/webservices/"> > > <xs:import namespace="http://example.co.za/claim/zmf" schemaLocation="https://dev.example.ws:8081/webservices/Claim?xsd=ZietoClaim_2_1.xsd"/> >  > > <wsdl:service name="ClaimService"> > <wsdl:port binding="tns:ClaimServiceSoapBinding" name="ClaimWSPort"> > <soap12:address location="https://dev.example.ws:8081/webservices/ZMF"/> > </wsdl:port> > </wsdl:service>}} > The XSD referenced inside the WSDL contains 2 more import statements to import 2 more XSD's. This is however where the problem starts. In the extract below you will notice that the schema location uses http and not https for the other 2 XSD's. > {{<?xml version='1.0' encoding='UTF-8'?> > <xsd:schema xmlns:zdt="http://example.co.za/claim/zmf/datatypes" xmlns:zcdt="http://example.co.za/common/datatypes" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://example.co.za/claim/zmf" elementFormDefault="qualified" > targetNamespace="http://example.co.za/claim/zmf"> > > <xsd:import namespace="http://example.co.za/claim/zmf/datatypes" schemaLocation="http://dev.example.ws:8081/webservices/Claim?xsd=zmf_dt_2_1.xsd"/> > <xsd:import namespace="http://example.co.za/common/datatypes" schemaLocation="http://dev.example.ws:8081/webservices/Claim?xsd=zdt_1_2.xsd"/> }} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 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 May 2018