[axistools-maven-plugin] the pre-downloading of WSDL's causes includes schema's
not to be found
-----------------------------------------------------------------------------------------------
Key: MOJO-321
URL: http://jira.codehaus.org/browse/MOJO-321
Project: Mojo
Type: Bug
Components: axistools
Environment: Linux, Debian testing
Reporter: Rene Clerc
I've encountered some problems with the axistools-maven-plugin.
First of all, I think the plugin should depend on (at least) axis 1.3 -- I've
spent some time dealing with options that weren't passed correctly
to the WSDL2Java. However, this may have had to do with incorrect dependencies.
The real problem lies with the following: when supplied with one or more URLs
denoting a WSDL, the plugin downloads these WSDLs (and en passant renames them
to a "safe" filename). It is then passed to axis WSDL2Java. If, however, such a
WSDL includes an XML schema, this is resolved locally, i.e. on the filesystem.
This means that my schema cannot be found, because it resids on the same HTTP
server as the WSDL and is therefore not yet downloaded.
I assume, by looking at the code, this prefetching of the WSDLs is done to
check whether the re-generating of the Java files is necessary or not. However,
this breaks my code generation.
I have fixed the problem for myself by bypassing the downloading and instead
supplying the urls directly to WSDL2Java. This "works for me". I can supply a
patch if necessary.
I would be glad to help out inventing a more robust solution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
