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.
Difficulty converting Stylesheet Class to XML String

Difficulty converting Stylesheet Class to XML String

2005-10-04       - By Brian Frutchey
Reply:     1     2     3     4  

I am attempting to build a quick JNI bridge between Xalan-J and Xalan-C++ such
that a single-threaded windows application won't take so long to transform
large mime messages with embedded base-64 encoded content (even with XSLTC a
12MB file takes 3 minutes and 85MB RAM to transform in Xalan-J, Xalan-C++
knocks it out in less than a second).  I am looking to pass the xml source,
xslt, and result across the JNI interface as strings.  However, I can't
understand how to get the org.apache.xalan.templates.Stylesheet class used by
the TransformerFactoryImpl to build an XML string from its contents.  I built
my own ContentHandler instead of using the org.apache.xalan.processor
.StylesheetHandler, and I can simply build the XML String from the SAX events
(which then works with my JNI interface), however I have difficulty supporting
namespaces and am fairly certain I will never implement the w3c requirements in
full, so it is not very good for general-use.  Hence I am wanting to override
the existing xalan classes.  The only problem I seem to have is getting the
Stylesheet out of the class as a string.  I tried treating the stylesheet as a
node tree and walking it, but can't seem to find the root node (getParent() is
always null).  Any ideas?  Thanks.

This email message and any attachments are confidential to Endeca. If you are
not the intended recipient, please notify Endeca immediately -- by replying to
this message or by sending an email to: legal@(protected) -- and destroy all
copies of this message and any attachments. Thank you.



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Difficulty converting Stylesheet Class to XML String</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=2 FACE="Arial">I am attempting to build a quick JNI bridge
between Xalan-J and Xalan-C++ such that a single-threaded windows application
won't take so long to transform large mime messages with embedded base-64
encoded content (even with XSLTC a 12MB file takes 3 minutes and 85MB RAM to
transform in Xalan-J, Xalan-C++ knocks it out in less than a second).&nbsp; I
am looking to pass the xml source, xslt, and result across the JNI interface as
strings.&nbsp; However, I can't understand how to get the org.apache.xalan
.templates.Stylesheet class used by the TransformerFactoryImpl to build an XML
string from its contents.&nbsp; I built my own ContentHandler instead of using
the org.apache.xalan.processor.StylesheetHandler, and I can simply build the
XML String from the SAX events (which then works with my JNI interface),
however I have difficulty supporting namespaces and am fairly certain I will
never implement the w3c requirements in full, so it is not very good for
general-use.&nbsp; Hence I am wanting to override the existing xalan classes.
&nbsp; The only problem I seem to have is getting the Stylesheet out of the
class as a string.&nbsp; I tried treating the stylesheet as a node tree and
walking it, but can't seem to find the root node (getParent() is always null).
&nbsp; Any ideas?&nbsp; Thanks.</FONT></P>

</BODY>
<!--[object_id=#endeca.com#]--><FONT face=Tahoma size=2><FONT color=#0000ff>
<FONT size=2>
<P>This email message and any attachments are confidential to Endeca. If you
are not the intended recipient, please notify Endeca immediately -- by replying
to this message or by sending an email to: legal@(protected) -- and destroy all
copies of this message and any attachments. Thank you.</P></FONT></FONT></FONT>
</HTML>