[
http://jira.codehaus.org/browse/MXMLBEANS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116605
]
Kyle Lebel commented on MXMLBEANS-42:
-------------------------------------
That's fine, I actually started poking around and found 1 issue which may be
the root cause of both issues I mentioned above. inside the "getFiles()"
method, which gets called from both getWsdlFiles() / getXsdFiles(), it sets
"results = null", then checks if the provided schemFiles is null, it skips all
the logic and returns a potentially null result.
Since we can provide "schemaFiles" as a method argument, I initialize "results"
to "schemaFiles". This way if it does skip the logic it will return what was
originally provided, which I believe was the intent of this condition. I'll
continue with my tests and let you know if I run into any other issues.
> plugin does not parse wsdl files
> --------------------------------
>
> Key: MXMLBEANS-42
> URL: http://jira.codehaus.org/browse/MXMLBEANS-42
> Project: Maven 2.x Xmlbeans Plugin
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: Kyle Lebel
> Attachments: pom.xml, xmlbeans-42.patch, xmlbeans-42.rar,
> xmlbeans-42a.rar, xmlbeans-42b.rar
>
>
> I could not find any information on this online. But I know xmlbeans
> supports generating from a wsdl file. Will the maven xmlbeans plugin support
> this in the future? For now I can rip the xsd's out from the wsdl and it
> seems to work fine this way. But I'd rather not have this extra step
> everytime there's an update to the web service.
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
