[jira] [Resolved] (CXF-6822) CLONE - java2ws -createxsdimports with packages that reference other packages should have schemaLocation in schema import

["Daniel Kulp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-6822.
------------------------------
       Resolution: Cannot Reproduce
    Fix Version/s: Invalid


Nothing attached to THIS jira and the sample attached to the linked jira produces XSD files that have the proper schemaLocation attribute:

{code:xml}
<xs:import namespace="http://test.cxf.apache.org" schemaLocation="JaxbService_schema1.xsd"/>
{code}

> CLONE - java2ws -createxsdimports with packages that reference other packages should have schemaLocation in schema import
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-6822
>                 URL: https://issues.apache.org/jira/browse/CXF-6822
>             Project: CXF
>          Issue Type: Bug
>          Components: Tooling
>    Affects Versions: 3.1.5
>         Environment: CXF 3.1.5, Windows 7
>            Reporter: Matthieu Ghilain
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: Invalid
>
>
> Object in package A references another object in package B. Using -createxsdimports option in java2ws creates schema imports and schemaLocation values properly in the .wsdl file but not in the .xsd files. <It creates xs:import namespace="value"> without the schemaLocation="" attribute, causing validation in most xml validators to fail. Workaround is to not use -createxsdimports, so that everything is generated in a single wsdl file, which validates properly. However, the schema files are more readable and reusable when created in separate files, instead of inline within the wsdl file.
> Attached sample demonstrates this issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)