This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
TRAX API in JAXP 1.1 - Parameters
- To: xsl-list at lists dot mulberrytech dot com
- Subject: [xsl] TRAX API in JAXP 1.1 - Parameters
- From: Dylan Walsh <Dylan dot Walsh at Kadius dot com>
- Date: Tue, 20 Feb 2001 17:13:05 -0000
- Reply-To: xsl-list at lists dot mulberrytech dot com
I am posting this here under the assumption that one of more of the
contributors to TRAX read this list.
I've been trying out the new version of this XML API for Java. It now
includes TRAX, the API for using XSL processors.
On the Transformer class there is a method for setting parameters which are
passed to params in the transformation:
setParameter(java.lang.String name, java.lang.Object value)
The second parameter is:
"value - The value object. 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."
This coersion is not specified. I wrote a class to test setting a param with
a nodeset. The JAXP implementation comes with Xalan, and to get my class to
work I had to use org.apache.xpath.objects.XNodeSet. This makes my code
dependent on the fact that the transformer being used is Xalan, defeating
the object of TRAX.
I would propose that classes/interfaces for the different standard parameter
types be included in TRAX. For example the classes in Xalan
(org.apache.xpath.objects package) are:
XBoolean
XBooleanStatic
XNodeSet
XNull
XNumber
XObject
XRTreeFrag
XString
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list