[
https://issues.apache.org/jira/browse/AXIS2-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael B updated AXIS2-4969:
-----------------------------
Attachment: wsdltocodebug.zip
> A problem using org.apache.axis2:axis2-wsdl2code-maven-plugin when wsdlFile
> is specified via "file:..." and the WSDL reffers to a XSD schema via relative
> path
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4969
> URL: https://issues.apache.org/jira/browse/AXIS2-4969
> Project: Axis2
> Issue Type: Bug
> Components: wsdl
> Affects Versions: 1.5.4
> Reporter: Michael B
> Priority: Minor
> Attachments: wsdltocodebug.zip
>
>
> There is a problem when using org.apache.axis2:axis2-wsdl2code-maven-plugin
> to generate code from a WSDL which reffers to a XSD schema via relative path,
> and when at the same time the maven plugin is configured like this - note
> URL-like path to the WSDL:
> <configuration>
>
> <wsdlFile>file:${basedir}/src/main/resources/service.wsdl</wsdlFile>
> <packageName>com.wsdltocode.bug</packageName>
> </configuration>
> The problem is that plugin searches for the XSD not only relative to the WSDL
> location, but also relative to the project root, and fails if either of them
> is not found. So that i have to have 2 XSD copies in my project due to that -
> one next to the WSDL and another in the project's root in order to be able to
> build. Take and build the attached maven project to reproduce the error.
> Possible walkaround is to change from
> "<wsdlFile>file:${basedir}/src/main/resources/service.wsdl</wsdlFile>" to
> "<wsdlFile>src/main/resources/service.wsdl</wsdlFile>", then no XSD is needed
> in root of the project.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
