XML processing/transforming approaches

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 ...

XML processing/transforming approaches

XML processing/transforming approaches

2003-04-24 - By Tung Tran

Hello everyone,

Im working on a XML processing application using Xerces / Xalan. Data will
pass two parsers before being transformed to HTML. Im considering between
two approaches:

1 Putting two parsers in two threads and connecting them with a piped
stream (PipedReader/PipedWriter).
2 Using 2 XMLFilter objects to join the parsers.

Id like to ask if any of you have experience with similar situation (I
guess its fairly common), especially in terms of performance.

Thanks in advance,
Tung Tran

<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas
-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 9">
<meta name=Originator content="Microsoft Word 9">
<link rel=File-List href="cid:filelist.xml@(protected)">

<style>

</style>
</head>

<body lang=EN-US style='tab-interval:36.0pt'>

<div class=Section1>

Hello everyone,<o:p></o:p>

<![if !supportEmptyParas]> <![endif]><o:p></o:p>

I’m working on a XML processing application using Xerces / Xalan.
Data
will pass two parsers before being transformed to HTML. I’m considering
between
two approaches:<o:p></o:p>

<![if !supportEmptyParas]> <![endif]><o:p></o:p>

1 – Putting two parsers in two threads and connecting them with a
piped
stream (PipedReader/PipedWriter).<o:p></o:p>

2 – Using 2 XMLFilter objects to join the parsers.<o:p></o:p>

<![if !supportEmptyParas]> <![endif]><o:p></o:p>

I’d like to ask if any of you have experience with similar
situation (I
guess it’s fairly common), especially in terms of performance.<o:p></o:p>


<![if !supportEmptyParas]> <![endif]><o:p></o:p>

Thanks in advance,<o:p></o:p>

Tung Tran<o:p></o:p>

</div>

</body>

</html>