[
https://issues.apache.org/jira/browse/XALANJ-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149768#comment-14149768
]
Andrey Aleshnikov commented on XALANJ-915:
------------------------------------------
[[email protected]], DOM Level 3 allows to attach DocumentType to a
{{Document}}:
{quote}
This node can be set at document creation time *and later changed* through the
use of child nodes manipulation methods, such as {{Node.insertBefore}}, or
{{Node.replaceChild}}.
{quote}
http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#ID-B63ED1A31
And people are already using this: http://stackoverflow.com/a/1409857
Can you please implement the DOCTYPE population with the DOMResult?
Considering the fact that Oracle JDK's JAXP implementation is using Xalan, I
guess that the positive impact of such a change will be great.
> DOMResult and StreamResult differ on adding DOCTYPE
> ---------------------------------------------------
>
> Key: XALANJ-915
> URL: https://issues.apache.org/jira/browse/XALANJ-915
> Project: XalanJ2
> Issue Type: Bug
> Components: transformation, Xalan-interpretive
> Affects Versions: 2.3Dx
> Environment: Operating System: All
> Platform: All
> Reporter: Kevin Ross
> Attachments: ASF.LICENSE.NOT.GRANTED--TransformationTest_1.java,
> ASF.LICENSE.NOT.GRANTED--hello.xsl, ASF.LICENSE.NOT.GRANTED--request.xml,
> ASF.LICENSE.NOT.GRANTED--transformed.xhtml
>
>
> using v2.3.1
> The DOMResult is not populated with the DOCTYPE, though StreamResult is.
> This
> is shown in the attached JUnit test case. Whether or not this is a spec
> issue,
> it is imperative for both results to be consistent.
> attached files:
> request.xml
> hello.xsl
> transformed.xhtml
> keywords: xhtml missing doctype DOM Document transform
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
