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.
Thoughts on Transformer parameter passing

Thoughts on Transformer parameter passing

2007-05-24       - By Eric J. Schwarzenbach
Reply:     1     2     3  

Reading some of the recent messages about parameter passing, lead me to
considering some of my own parameter passing code habits, and to look at
the documentation again.

The Javadoc for javax.xml.transform.Transformer.setParameter(name,
value) says of value "This can be any valid Java object. It is up to the
processor to provide the proper object coersion or to simply pass the
object on for use in an extension." (It's not clear to me if it is
assumed there is a single "proper" mapping of Java objects to XSLT
constructs, or if that too is up to the implementation to decide.)

On the Xalan-Java site, the FAQ is silent on parameter passing, and the
Usage Patterns just refers to the UseStylesheetParam.java sample. That
sample shows only the simplest most obvious case, passing a String.

This topic seems to cry out for treatment in the FAQ. At the very least
shouldn't Xalan's mapping of Java objects to XSLT constructs be
documented somewhere?

Where I work, we typically pass XML fragments as parameters, by creating
a Document and the necessary Element, Atribute and Text nodes with a
DocumentBuilder, and then putting that into a NodeList (currently we
have a very simple ArrayList-based implementation of that interface that
we use for that purpose) and pass that. I cannot remember what
combination of trial and error and searching the web for random postings
on the matter that resulted in our arriving at this procedure, and I'm
by no means confident that this is the best way to go about it. I do
recall having seen it struggled with at several companies I've worked at
prior to getting into the XSLT side of things myself, due to the general
scarcity of good information on the topic.

Also, reading the recent posts and their references gives me no idea if
the practice I outlined above will continue to work if we start using
XSLTC, and if not, whether that should be considered a bug or simply a
limitation of the how this implementation chooses to do its object
coersion. Can someone tell me?

Eric