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

2006-12-27       - By Ziv Ben-Eliahu
Reply:     1     2     3     4     5     6  

Hi There.
I have a similar problem - fails for DOMSource but succeeds for
StreamSource - but failure is not an error, it is a different output.

I have the following XML:
<apple xmlns="http://purl.oclc.org/NET/JSX/0.3/Apple">
    <shop type="happy-days">
        <owner name="Jhon" type="big"/>
    </shop>
    <order name="GooGoo" type="org.goo" />
</apple>

I have two parsers - an identity-transformer and a xsl-transformer :
        Transformer tfCopy = javax.xml.transform.TransformerFactory
                              .newInstance().newTransformer();
        Transformer tf = javax.xml.transform.TransformerFactory
                        .newInstance()newTransformer(
                           new StreamSource(new File("Apple.xsl")));

I have three source type - by stream, builder-parsed, builder-created:
Document parsedDoc = builder.parse(new File("apple.xml"));
DOMSource parsedSource = new DOMSource(parsedDoc);
StreamSource streamSource = new StreamSource(new File("apple.xml"));
DOMSource builtSource = new DOMSource(build());  // build() is a manual
build of the parsed document


When I use the identity-transformer the results are the same:
        tfCopy.transform(streamSource, new StreamResult(new
File("d:/streamed.xml")));
        tfCopy.transform(builtSource, new StreamResult(new
File("d:/built.xml")));
        tfCopy.transform(parsedSource, new StreamResult(new
File("d:/parsed.xml")));



When I use the XSL-based-transformer, results are completely different.
        tf.transform(builtSource, new StreamResult(new
File("d:/built.html")));
        tf.transform(parsedSource, new StreamResult(new
File("d:/parsed.html")));
        tf.transform(streamSource, new StreamResult(new
File("d:/streamed.html")));


I won't include them since they are long, but to sum up:
The stream-source gave the expected results.
The parsed-dom-source (from the same file as the stream-source) gave bad
results - its like the Document was not recognized.
The manually-built-dom-source gave the expected results.


Question: how come identity-transformer worked fine with the parsed DOM
and a xsl-transformer did not?


My current solution is:
Use the identity-transformer to copy from the parsed-dom to a
result-dom. Then take the node from the result-dom. The XSL-transformer
works fine with that node.

Thank you for your help,
Ziv.



SORENS,MICHAEL (HP-Boise,ex1) wrote:
> I want to do a transform with a DOMSource input. If I do this from a file
> (i.e. StreamSource), it works fine, but changing only the argument to
> transform() to be a DOMSource, then the transformation fails with a
> HIERARCHY_REQUEST_ERR. I boiled down a test for this to its simplest form,
> containing 80 lines of code below. This code performs one of three
> transforms (differing in type of argument) by invoking with "-A", "-B", or
> "-C". It uses supplementary files test.xml and test.xsl following.
> Question 1: Why does transform() fail if I use a DOMSource argument??
>
> I believe I am using Xalan 2.4.0 and Xerces 2.3.0.
> Question 2: How does one query Xalan/Xerces to find the version number?