Thoughts on Transformer parameter passing 2007-05-24 - By Dave Brosius
I completely agree. It would great if a sample was available that showed
how to work with beans as parameters.
"Eric J. Schwarzenbach" <Eric.Schwarzenbach@(protected)>
05/24/2007 04:16 PM
To
xalan-j-users@(protected)
cc
Subject
Thoughts on Transformer parameter passing
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
<br><font size=2 face="sans-serif">I completely agree. It would great if
a sample was available that showed how to work with beans as parameters.</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Eric J. Schwarzenbach
"
<Eric.Schwarzenbach@(protected)></b> </font>
<p><font size=1 face="sans-serif">05/24/2007 04:16 PM</font>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">xalan-j-users@(protected)<
/font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Thoughts on Transformer parameter
passing</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>Reading some of the recent messages about parameter
passing, lead me to<br>
considering some of my own parameter passing code habits, and to look at<br>
the documentation again.<br>
<br>
The Javadoc for javax.xml.transform.Transformer.setParameter(name,<br>
value) says of value "This can be any valid Java object. It is up
to the<br>
processor to provide the proper object coersion or to simply pass the<br>
object on for use in an extension." (It's not clear to me if it is<br>
assumed there is a single "proper" mapping of Java objects to
XSLT<br>
constructs, or if that too is up to the implementation to decide.)<br>
<br>
On the Xalan-Java site, the FAQ is silent on parameter passing, and the<br>
Usage Patterns just refers to the UseStylesheetParam.java sample. That<br>
sample shows only the simplest most obvious case, passing a String.<br>
<br>
This topic seems to cry out for treatment in the FAQ. At the very least<br>
shouldn't Xalan's mapping of Java objects to XSLT constructs be<br>
documented somewhere?<br>
<br>
Where I work, we typically pass XML fragments as parameters, by creating<br>
a Document and the necessary Element, Atribute and Text nodes with a<br>
DocumentBuilder, and then putting that into a NodeList (currently we<br>
have a very simple ArrayList-based implementation of that interface that<br>
we use for that purpose) and pass that. I cannot remember what<br>
combination of trial and error and searching the web for random postings<br>
on the matter that resulted in our arriving at this procedure, and I'm<br>
by no means confident that this is the best way to go about it. I do<br>
recall having seen it struggled with at several companies I've worked at<br>
prior to getting into the XSLT side of things myself, due to the general<br>
scarcity of good information on the topic.<br>
<br>
Also, reading the recent posts and their references gives me no idea if<br>
the practice I outlined above will continue to work if we start using<br>
XSLTC, and if not, whether that should be considered a bug or simply a<br>
limitation of the how this implementation chooses to do its object<br>
coersion. Can someone tell me?<br>
<br>
Eric<br>
<br>
</tt></font>
<br>
|
|
