Good point - I can't see a way to set params into XMLFilters either.
But: all the API's you're talking about so far are either SAX or JAXP
standards, not necessarily Xalan-specific. So any XSLT processor that
claims to implement JAXP should work the same - I think Saxon and I
thought one other processor did too.
Couldn't you simply use a single tricky stylesheet that processed the
node and saved it in a variable, and then processed the variable to
provide the desired output? Is it strictly necessary that the
processes be done separately?
- Shane
---- you "Dean H. Saxe" <[EMAIL PROTECTED]> wrote ----
... Anyway, to recap for those who missed out, I am trying to process a
node
twice, in succession. Gary suggested using XMLFilter classes and
pulling
the XML document through multiple sequential filters. My only problem
is
that I need to dynamically set properties in the stylesheet at
runtime. Normally I would use: transformer.setParameter("foo",
"bar"); However, in the XMLFilter classes there appears to be no
method to
set parameters on the transformer contained within the XMLFilter. =-(
Another question is what other stylesheet processors support the use of
XMLFilters. I need to be able to use this technology with multiple
different XSL processors, just in case someone decides that a different
processor is "better" for whatever reason. -dhs
=====
<eof aka="mailto:[EMAIL PROTECTED]";
quote="Odo: [You'd shoot a man in the back?]
Garak: [Well, it's the safest way, isn't it?]"/>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger.
http://im.yahoo.com
