[
http://jira.codehaus.org/browse/MXMLBEANS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Corridor Software Developer updated MXMLBEANS-42:
-------------------------------------------------
Attachment: xmlbeans-42.patch
I attached a patch which represents the ugly first pass. You're correct, the
basic facilities for generating classes from wsdl's is there. I updated the
code to deal with the similarly to how xsd's are handled. Haven't refactored
for efficiency yet, or stepped through to watch for new behavior which would
result in new defects.
If you update the source with this patch and run against the test case you
provided (thanks for that, btw, big help), you will get duplicate class errors.
Does your experience with the scomp tool or others come with advice on how to
handle that? A flag or two that I should look at?
The patch is rooted in the xmlbeans-maven-plugin directory.
> 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: xmlbeans-42.patch, xmlbeans-42.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
