[
https://issues.apache.org/jira/browse/CXF-7489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145565#comment-16145565
]
ASF GitHub Bot commented on CXF-7489:
-------------------------------------
GitHub user facundovs opened a pull request:
https://github.com/apache/cxf/pull/308
CXF-7489: Stax2Validation doesn't support schema imports.
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:
```
<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>
```
As you can see in these cases, the targetNamespace is not present in the
schema element that is only used for importing external schemas.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/facundovs/cxf CXF-7489
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf/pull/308.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #308
----
commit 3f23269e61cf31f33e3e88e93cdaffaca6792efe
Author: facundov <[email protected]>
Date: 2017-08-29T14:32:53Z
CXF-7489: Stax2Validation doesn't support schema imports.
----
> 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
>
> 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)
