You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2012/10/03 03:46:07 UTC
[jira] [Commented] (CXF-4538) cxf-codegen-plugin wsdl2java fails
when you have nested projects
[ https://issues.apache.org/jira/browse/CXF-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468253#comment-13468253 ]
Daniel Kulp commented on CXF-4538:
----------------------------------
Can you create a simple test project?
The schemaLocation should be applied against the location of the wsdl/xsd that has the import. If that's not working, it may be having problems constructing a valid URL for the original WSDL.
> 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
>
> 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