http://JudithbdAlmonteefq.spaces.live.com
BAD MSG:
would happen when trying to use a variable holding a non-Xalan type in an XPath
expression. How would Xalan know the
orrect conversion from a non-Xalan type? There is a description of passing
non-Xalan arguments. I think this means
you'll have to nest the arguments without using interme
BAD MSG:
passed. If you want to include all of the markup, you'll need to hunt
round for a serializer that will take in a NodeIterator and produce a
string. I think there may be one in XalanJ or XercesJ but I haven't
delved into that. If you get stuck, please let us know and we'll look
around.
BAD MSG:
set happens to be a String object.
ow when I transform I get the output as the value of the Xpathname
parameter only, whereas If I declare a vraible inside the stylesheet and
give it the same value as I am giving to the parameter from outside I get
the desired result.
Is there some proble
BAD MSG:
expressed in Perl, Python, some other transformation markup language etc. So
e need a map between how the transformation is expressed and the processor
that can execute the transform. In JDBC something vaguely similar is
achieved through a list of drivers and "does anyone understand this
BAD MSG:
u can do is to create a new DOM and copy the required attributes (etcetra)
ith changed values..
Regards,
Ankur
-Original Message-
From: longinus [mailto:[EMAIL PROTECTED]
Sent: Friday, November 09, 2001 4:42 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: changing attribute
> is it better to share a single
> factory instance and synchronized on it or is it better to create a new
> factory instance for each thread?
I guess I would create a new one each time. But you should experement.
> would it be faster to use compiled translet objects or trax templates
> objects?