April 2018 - jbossws-issues - Jboss List Archives

[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 Viral Gohel (JIRA)

[ https://issues.jboss.org/browse/JBWS-4087?page=com.atlassian.jira.plugin.... ] Viral Gohel updated JBWS-4087: ------------------------------ > 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.1.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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4113) Wsprovide tool doesn't generate/keep class files on JDK9 or JDK10

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-4113?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-4113: -------------------------------- Fixed file.separator used in Jdk9PlusJBossModulesAwareCompiler. > Wsprovide tool doesn't generate/keep class files on JDK9 or JDK10 > ----------------------------------------------------------------- > > Key: JBWS-4113 > URL: https://issues.jboss.org/browse/JBWS-4113 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.2.Final > Reporter: R Searls > Assignee: R Searls > Fix For: jbossws-cxf-5.2.1.Final > > > CXFProviderImpl using apache's JavaToWS does not provide a means to provide a custom compiler implementation like CXFConsumerImpl using apache's WSDLToJava does. > Changes are needed to CXFProviderImpl and code related to apache's JavaToWS to accept and use a custom compiler like WSDLToJava does. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4115) antrun-wsconsume.xml antrun-wsprovider.xml fails on Windows

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-4115?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-4115: -------------------------------- The wsconsume-macro(s) for target wsconsumeWindows is missing the property additional.jvm.args="${additional.jvm.args}" This property is declared on the target wsconsumeNotWindows wsconsume-macro(s). > antrun-wsconsume.xml antrun-wsprovider.xml fails on Windows > ----------------------------------------------------------- > > Key: JBWS-4115 > URL: https://issues.jboss.org/browse/JBWS-4115 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.1.Final > Reporter: R Searls > Assignee: R Searls > > integration-tests do not run on Windows 10. The antrun-ws*.xml scripts fail with error > additional.jvm.args is missing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4115) antrun-wsconsume.xml antrun-wsprovider.xml fails on Windows

by R Searls (JIRA)

R Searls created JBWS-4115: ------------------------------ Summary: antrun-wsconsume.xml antrun-wsprovider.xml fails on Windows Key: JBWS-4115 URL: https://issues.jboss.org/browse/JBWS-4115 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-5.2.1.Final Reporter: R Searls Assignee: R Searls integration-tests do not run on Windows 10. The antrun-ws*.xml scripts fail with error additional.jvm.args is missing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4114) DOMUtils incorrectly assumes presence of DocumentBuilderFactory on all CLs

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4114?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4114: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.1.Final > DOMUtils incorrectly assumes presence of DocumentBuilderFactory on all CLs > -------------------------------------------------------------------------- > > Key: JBWS-4114 > URL: https://issues.jboss.org/browse/JBWS-4114 > Project: JBoss Web Services > Issue Type: Bug > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: jbossws-cxf-5.2.1.Final > > > {noformat} > 2018-04-20 08:26:22,740 ERROR [stderr] (default task-1) javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found > 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at java.xml/javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:194) > 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at java.xml/javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:147) > 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at java.xml/javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:184) > 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils$1.initialValue(DOMUtils.java:113) > 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils$1.initialValue(DOMUtils.java:100) > 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at java.base/java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:180) > 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at java.base/java.lang.ThreadLocal.get(ThreadLocal.java:170) > 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils.getDocumentBuilder(DOMUtils.java:200) > 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils.parse(DOMUtils.java:250) > 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils.parse(DOMUtils.java:211) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4114) DOMUtils incorrectly assumes presence of DocumentBuilderFactory on all CLs

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBWS-4114?page=com.atlassian.jira.plugin.... ] David Lloyd updated JBWS-4114: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-common/pull/11 > DOMUtils incorrectly assumes presence of DocumentBuilderFactory on all CLs > -------------------------------------------------------------------------- > > Key: JBWS-4114 > URL: https://issues.jboss.org/browse/JBWS-4114 > Project: JBoss Web Services > Issue Type: Bug > Reporter: David Lloyd > Assignee: David Lloyd > > {noformat} > 2018-04-20 08:26:22,740 ERROR [stderr] (default task-1) javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found > 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at java.xml/javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:194) > 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at java.xml/javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:147) > 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at java.xml/javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:184) > 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils$1.initialValue(DOMUtils.java:113) > 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils$1.initialValue(DOMUtils.java:100) > 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at java.base/java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:180) > 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at java.base/java.lang.ThreadLocal.get(ThreadLocal.java:170) > 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils.getDocumentBuilder(DOMUtils.java:200) > 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils.parse(DOMUtils.java:250) > 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils.parse(DOMUtils.java:211) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4114) DOMUtils incorrectly assumes presence of DocumentBuilderFactory on all CLs

by David Lloyd (JIRA)

David Lloyd created JBWS-4114: --------------------------------- Summary: DOMUtils incorrectly assumes presence of DocumentBuilderFactory on all CLs Key: JBWS-4114 URL: https://issues.jboss.org/browse/JBWS-4114 Project: JBoss Web Services Issue Type: Bug Reporter: David Lloyd Assignee: David Lloyd {noformat} 2018-04-20 08:26:22,740 ERROR [stderr] (default task-1) javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at java.xml/javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:194) 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at java.xml/javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:147) 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at java.xml/javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:184) 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils$1.initialValue(DOMUtils.java:113) 2018-04-20 08:26:22,741 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils$1.initialValue(DOMUtils.java:100) 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at java.base/java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:180) 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at java.base/java.lang.ThreadLocal.get(ThreadLocal.java:170) 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils.getDocumentBuilder(DOMUtils.java:200) 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils.parse(DOMUtils.java:250) 2018-04-20 08:26:22,742 ERROR [stderr] (default task-1) at org.jboss.ws.common@3.2.0.Final//org.jboss.ws.common.DOMUtils.parse(DOMUtils.java:211) {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

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

by Radovan Netuka (JIRA)

[ https://issues.jboss.org/browse/JBWS-4064?page=com.atlassian.jira.plugin.... ] Radovan Netuka updated JBWS-4064: --------------------------------- Git Pull Request: https://github.com/jboss/cxf/pull/20 > 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: Radovan Netuka > Fix For: jbossws-cxf-5.2.1.Final > > Attachments: mtomExample.war > > > Check issue, https://issues.apache.org/jira/browse/CXF-7317 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

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

by Radovan Netuka (JIRA)

[ https://issues.jboss.org/browse/JBWS-4064?page=com.atlassian.jira.plugin.... ] Radovan Netuka commented on JBWS-4064: -------------------------------------- This one is curious. According to [RFC-2392|https://tools.ietf.org/html/rfc2392]: "A *cid* URL is converted to the corresponding Content-ID message header [MIME] by removing the *cid:* prefix, _converting the % encoded character to their equivalent US-ASCII characters_, and enclosing the remaining parts with an angle bracket pair, *<* and *>*... Reversing the process and _converting URL special characters to their % encodings_ produces the original cid." But few lines later, they provide an example that contradicts the provided information: "For example, *cid:foo4%25foo1@bar.net* corresponds to *Content-ID: <foo4%25foo1(a)bar.net>*" The same RFC document clearly says, that *cid:...* element _must_ be encoded. I wasn't able to find any information on Content-ID however. For me, the only possible solution is not to fix the cid element not to be encoded (as suggested upstream), but to fix the Content-ID header _to be encoded_. > 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: Radovan Netuka > Fix For: jbossws-cxf-5.2.1.Final > > Attachments: mtomExample.war > > > Check issue, https://issues.apache.org/jira/browse/CXF-7317 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

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

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4064?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4064: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.1.Final > 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: Radovan Netuka > Fix For: jbossws-cxf-5.2.1.Final > > Attachments: mtomExample.war > > > Check issue, https://issues.apache.org/jira/browse/CXF-7317 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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