[forge-dev] [JBoss JIRA] Updated: (SEAMFORGE-179) An XML document parsed with the Forge XMLParser cannot be exported with XMLParser#toXML if it contains comments

[Lincoln Baxter III (JIRA)]

     [ https://issues.jboss.org/browse/SEAMFORGE-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lincoln Baxter III updated SEAMFORGE-179:
-----------------------------------------

           Status: Closed  (was: Pull Request Sent)
         Assignee: Kevin Pollet
    Fix Version/s: 1.0.0.Alpha4
       Resolution: Done


Done!

> An XML document parsed with the Forge XMLParser cannot be exported with XMLParser#toXML if it contains comments
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: SEAMFORGE-179
>                 URL: https://issues.jboss.org/browse/SEAMFORGE-179
>             Project: Seam Forge
>          Issue Type: Bug
>          Components: Parsers / File Manipulation
>    Affects Versions: 1.0.0.Alpha3
>            Reporter: Kevin Pollet
>            Assignee: Kevin Pollet
>            Priority: Blocker
>             Fix For: 1.0.0.Alpha4
>
>
> When the {{XMLParser#parse}} method is called on a stream which contains comments, DOM creates a Node named "#comment" and the corresponding Node is created by Forge parser. After that, when the {{XMLParser#toXML}} method is called on the XML root node an exception is thrown. 
> At serialization Forge parser tries to create a Node with name "#comment" by using the method {{Document#createElement}} (which is illegal and result in a {{DOMException#INVALID_CHARACTER_ERR}}) instead of calling the method {{Document#createComment}}. IMO, the same problem could happen with others specific nodes.
> Maybe Shrinkwrap descriptor project could have the same problem, but it needs further investigations...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira