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.
set a Node Parameter in the Transformer class

set a Node Parameter in the Transformer class

2007-05-28       - By Henry Zongaro
Reply:     1     2  

Hi, Stanislas.

Giraudet de Boudemange <stanislas.giraudet-de-boudemange@(protected)> wrote
on 2007-05-28 06:57:27 AM:
> I have a problem with the setParameter method in the Transformer class
> of xalan.
> I want to pass a Node parameter (a DOM element), but this node is always

> transform in
> a String with the toString() method of the node.

Looking at your output, it looks to me like you are using XSLTC.  This is
a known limitation with XSLTC.  See Jira issue XALANJ-1552 [1] for
example.

Would using Xalan-J Interpretive be an option for you?  That processor
does have support for supplying a DOM Node as a parameter value,  but note
that you will have to change the line in your source that creates the
DOMSource for the input document to the following:

          DOMSource source=new DOMSource( docSource);

That's because of another bug in how the interpretive processor treats a
node argument to DOMSource that is not the root of a DOM tree.

I hope that helps.

Thanks,

Henry
[1] http://issues.apache.org/jira/browse/XALANJ-1552
------------------------------------------------------------------
Henry Zongaro      XSLT Processors Development
IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
mailto:zongaro@(protected)



<br><font size=2 face="sans-serif">Hi, Stanislas.</font>
<br>
<br><tt><font size=2>Giraudet de Boudemange &lt;stanislas.giraudet-de
-boudemange@(protected)&gt;
wrote on 2007-05-28 06:57:27 AM:<br>
&gt; I have a problem with the setParameter method in the Transformer class
<br>
&gt; of xalan.<br>
&gt; I want to pass a Node parameter (a DOM element), but this node is
always <br>
&gt; transform in<br>
&gt; a String with the toString() method of the node.<br>
</font></tt>
<br><font size=2 face="sans-serif">Looking at your output, it looks to
me like you are using XSLTC. &nbsp;This is a known limitation with XSLTC.
&nbsp;See Jira issue XALANJ-1552 [1] for example.</font>
<br>
<br><font size=2 face="sans-serif">Would using Xalan-J Interpretive be
an option for you? &nbsp;That processor does have support for supplying
a DOM Node as a parameter value, &nbsp;but note that you will have to change
the line in your source that creates the DOMSource for the input document
to the following:</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp
;DOMSource
source=new DOMSource( docSource);</font>
<br>
<br><font size=2 face="sans-serif">That's because of another bug in how
the interpretive processor treats a node argument to DOMSource that is
not the root of a DOM tree.</font>
<br>
<br><font size=2 face="sans-serif">I hope that helps.</font>
<br><font size=2 face="sans-serif"><br>
Thanks,<br>
<br>
Henry</font>
<br><font size=2 face="sans-serif">[1] http://issues.apache.org/jira/browse
/XALANJ-1552<br>
------------------------------------------------------------------<br>
Henry Zongaro &nbsp; &nbsp; &nbsp;XSLT Processors Development<br>
IBM SWS Toronto Lab &nbsp; T/L 969-6044; &nbsp;Phone +1 905 413-6044<br>
mailto:zongaro@(protected)</font>
<br>
<br>