Subjects
Home
Xalan extension functions
Fomatting question serializing DOM with pretty print
xalan with pull parser
Cannot find the declaration
Apache Xalan drop support to run on JRE 1 1 x
Why does Doctype change processing of a document
Node set to XML string via Java extensions in Xalan J: possible?
Templates/Transformers + thread safety???
Problem evaluating xpath with muliple prefix with different namespace
remove an arbitrary attribute from xsl output
Xalan3 XSLT 2 0 XPath 2 0 support?
Problem using compiled translets with Xalan !!
Xalan and jstl 1 1 problem with transform tag
NullPointer in DOM2DTM getLocalName
URIResolvers base parameter with xsltc and cascaded imports
Performance problem for Xalan J on intel dual core
Standard libraries in JAXP?
Serializing a DOM tree to XML file, customize entities replacement
Library Conflict Involving BCEL Library
A question on how users are using <xsl:message >
Kevin Cormier as a new Apache Xalan J committer
Struggling to iterate over tokenized string
Xalan count() trouble
Problem with recursive xpath
Error when switching to java 1 5
document( ' ')
Problem with Xalan2 7 0 transformation
cr/lf options
entity encoded XML
can xalan transform 2 xml using one xslt?
Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
xsl transform with cdata section elements
xslt parameters not expanded
Weird behavior of XPath evaluate()
How to avoid <xsl:message > instruction prints stylesheet file informations ?
Cannot find SimpleTransform subdirectory after installing Xalan J
recover from document not found exceptions
jdk1 5 and Xalan jar differences?
Performance Issue
Error/Bug adding floating point numbers
XPathAPI: eval exp using nodes with default namespace
modifying xalan to output invalid XML
NullPointerException
mege two separate xml nodes into one
Is this a XALAN document identification bug?
is StylesheetRoot really java io Serializable ?
transform() fails for DOMSource but succeeds for StreamSource
Thoughts on Transformer parameter passing
HELP, Xalan and jstl 1 1 problem with transformer
Problem with XPath namespace axis?
string utils:replace deleting search string if replacement string is an HTML
help with enumeration values pls
xalan 2 5 1 vs 2 7 performance question
How to insert/update in XML document
HTML Serialization and Handling of Ampersands in HREF Attributes
XHTML link tag stripping
SystemId Unknown; Line #24; Column #49; java lang NullPointerException
xpath text() help
Apostrophe problem with xalan 2 7 0
How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
transform() fails for DOMSource but succeeds for StreamSource

transform() fails for DOMSource but succeeds for StreamSource

2003-08-18       - By Dave Flanagan
Reply:     1     2     3     4     5     6  

Had originally sent the response shown below detailing the problem he was
having - but it did not make it to the userlist when I sent the response -
here it is again if any one was interested in what what happening

Dave Flanagan

Michael - making one of two changes should correct the problem you are
experiencing:
Solution #1:
   Instead of dealing with the Document Element of the source which you are
   obtaining with the following line:
       Element docRoot = db.parse(inName).getDocumentElement();
   change it to
       Document docRoot = db.parse(inName);
-------
Solution #2:
If no change to your java code is desired then
    in the stylesheet change
         <xsl:template match="/files">
    to
         <xsl:template match="files">

Dave Flanagan

----- Original Message -----
From: "Joseph Kesselman" <keshlam@(protected)>
To: <xalan-j-users@(protected)>
Sent: Monday, August 18, 2003 10:16 AM
Subject: Re: transform() fails for DOMSource but succeeds for StreamSource


>
>
>
>
> I strongly suspect you've misdiagnosed the problem, and your glitch is
tied
> to the use of a DOMResult rather than a DOMSource.
>
> When outputting to a DOM Document, your generated document *must* meet the
> DOM's well-formedness requirements -- single root element, no text nodes
> outside that root element, etc.  If you violate those constraints, the DOM
> will throw a HIERARCHY_REQUEST_ERR.
>
> I haven't analysed your testcase in detail, but if my guess is right your
> options are:
>
> 1) Fix the stylesheet to produce a well-formed XML document.
>
> 2) Output to SAX rather than DOM, since SAX doesn't enforce as many of the
> well-formedness constraints.
>
> 3) If you really need DOM and really something other than a well-formed
> document, you could try wrapping the DOMResult around a DocumentFragment
> rather than a Document. That would permit multiple top-level elements and
> text at the top level; depending on exactly what the system is complaining
> about, that might be enough to get you over the hump.
>
> ______________________________________
> Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
> "The world changed profoundly and unpredictably the day Tim Berners Lee
> got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
>
>