[ 
http://issues.apache.org/jira/browse/MUSE-100?page=comments#action_12439336 ] 
            
Dan Jemiolo commented on MUSE-100:
----------------------------------

Steve - Is there a reason you changed XmlUtils.moveSubTree() to copySubTree()? 
Right now, we use one DOM Document for our temporary XML fragments 
(XmlUtils.EMPTY_DOC), and this allows us to save a lot on copying because we 
don't have to use Document.importNode() as much. moveSubTree() altered the 
original Element, but since the original was never used after the new Element 
was created, this was a non-issue (and it saved us the unnecessary copying). 

I'll look at the code more closely tonight. Let me know if I'm missing 
something.


> Add better XSD support to wsdl2java
> -----------------------------------
>
>                 Key: MUSE-100
>                 URL: http://issues.apache.org/jira/browse/MUSE-100
>             Project: Muse
>          Issue Type: New Feature
>          Components: Tooling - Code Generation
>    Affects Versions: 2.0.0
>            Reporter: Steve Jerman
>         Assigned To: Dan Jemiolo
>             Fix For: 2.1.0
>
>         Attachments: modules.zip, patch.patch
>
>
> Attached is some code that implements signficantly better XSD handling. I 
> will do more testing on this, but thought I would make an initial 
> contribution now since I ended up fixing some bugs whist implementing it. I 
> also need to do a spin of the code to improve the comments and remove some 
> debug code... but it does work I think.
> Someof this code my be useful for v2.0.0.....
> Description of functionality.
> In addtion to existing functionality, it 
> * Allows use of the type attribute in WSRP property GEDs. 
> * Allow use of xs:extension in resource property document defintions.
> Bugs fixed:
> - Nested XSD includes did not work. There were several nested bugs.. since 
> the contents of a schema were moved, no includes were found. Once I got that 
> working, the recursive inclusion ran away.
> - Type resolution needed some work since qName prefixs did not resolve 
> correctly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
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]

Reply via email to