You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Dennis Kieselhorst (JIRA)" <ji...@apache.org> on 2017/09/02 07:11:02 UTC
[jira] [Resolved] (CXF-7489) Stax2Validation doesn't support schema
imports.
[ https://issues.apache.org/jira/browse/CXF-7489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Kieselhorst resolved CXF-7489.
-------------------------------------
Resolution: Fixed
Assignee: Daniel Kulp
> Stax2Validation doesn't support schema imports.
> -----------------------------------------------
>
> Key: CXF-7489
> URL: https://issues.apache.org/jira/browse/CXF-7489
> Project: CXF
> Issue Type: Bug
> Reporter: Facundo Velazquez
> Assignee: Daniel Kulp
> Fix For: 3.2.0
>
>
> Using the Stax2Validation for validating a wsdl, a NPE is being thown.
> After some analysis I could find that the targetNamespace is being used as key to save schemas to process (please see [this code line|https://github.com/apache/cxf/blob/master/core/src/main/java/org/apache/cxf/staxutils/validation/Stax2ValidationUtils.java#L153])
> However, a WSDL can have the following format in the <wsdl:types> element:
> {code:xml}
> <wsdl:types>
> <xsd:schema>
> <xsd:import namespace="http://www.foo.org" schemaLocation="foo.xsd"/>
> <xsd:import namespace="http://www.bar.org" schemaLocation="bar.xsd"/>
> </xsd:schema>
> </wsdl:types>
> {code}
> As you can see in these cases, the targetNamespace is not present in the schema element that is only used for importing external schemas.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)