[
https://issues.apache.org/jira/browse/CXF-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468602#comment-13468602
]
Daniel Kulp commented on CXF-4538:
----------------------------------
The bug is actually the "reverse". The problem is that it should ALSO fail in
SubModule1 and isn't. Per spec, relative locations for the imports should be
resolved based from the location of the wsdl. Thus, it should be resolved
from SubProject1/src/main/resources and should then look for the schema in
SubProject1/src/main/SubProject2/src/main/resources/shiporder.xsd which
obviously doesn't exist. That it's NOT doing that properly is likely a bug.
The import in the wsdl should likely be updated to:
<xsd:import namespace ="http://testproject2.apache.my/";
schemaLocation="../../../../SubProject2/src/main/resources/shiporder.xsd" />
which would make it correct as well as make it properly work from both
locations.
> cxf-codegen-plugin wsdl2java fails when you have nested projects
> ----------------------------------------------------------------
>
> Key: CXF-4538
> URL: https://issues.apache.org/jira/browse/CXF-4538
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.6.2
> Environment: Linux
> Reporter: Andrew Burks
> Priority: Critical
> Labels: build, maven
> Attachments: ApacheTestProject.tar
>
>
> In my wsdl, I am importing and xsd from another maven project and I provide a
> relative path to the xsd. When executing mvn clean install on this
> sub-project, call it project A, the project builds as expected. After
> navigating to Project A's parent project and executing mvn clean install, I
> receive a java.io.FileNotFoundException because the relative path provided in
> the import of Project A's wsdl was relative to Project A. I can only assume
> that wsdl2java uses the "current build directory" when applying the
> schemaLocation attribute from an import.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
