[ 
https://issues.apache.org/jira/browse/AXIOM-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen resolved AXIOM-437.
-----------------------------------

    Resolution: Fixed

Fixed. Note that the fix required an incompatible API change, namely of the 
OMDocType interface and the signature of the createOMDocType method in 
OMFactory. The reason is that OMDocType had a single property "value". For an 
OMDocType node created by a builder, this property stored the internal subset. 
On the other hand, to be serialized properly, this property was expected to 
store the entire DOCTYPE declaration. There is no way to make this consistent 
without changing the interface.

Since in Axiom <= 1.2.13 support for DOCTYPE is basically broken, it is 
expected that this change has no impact on existing application code.
                
> OMDocType not serialized correctly
> ----------------------------------
>
>                 Key: AXIOM-437
>                 URL: https://issues.apache.org/jira/browse/AXIOM-437
>             Project: Axiom
>          Issue Type: Bug
>          Components: API, DOOM, LLOM
>    Affects Versions: 1.2.13
>            Reporter: Andreas Veithen
>            Assignee: Andreas Veithen
>            Priority: Minor
>             Fix For: 1.2.14
>
>
> Documents containing a DOCTYPE declaration are not round-trippable. When 
> serializing a document that contains such an information item, the output is 
> not well formed.
> The issue can be traced back to an incorrect usage of the StAX API: for a DTD 
> event, XMLStreamReader#getText() returns only the internal subset, but 
> XMLStreamWriter#writeDTD expects the entire DOCTYPE declaration as input.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.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