Steve,
At 05:05 PM 12/16/2003, you wrote:
I'm starting to get the sinking feeling that what I need to do isn't
possible using XSLT alone, and I'm going to need to come up with some hack
the post-processes a new DOM tree and copies the results into the tree I
want. It's not the solution I was hoping for, but nothing better seems to be
presenting itself...
I think you're right about this. XSLT doesn't address how its input is
produced or how its output is handled, beyond some guidance about how
settings in <xsl:output/> may be respected by a serializer, which obviously
doesn't pertain to your case.
From the perspective of the XSLT process, there is an input document and
an output "result tree". These are two different things. There's no notion
of replacing one tree with another, or adding to or modifying a tree that
already exists, though a calling environment might well do this. It really
seems like yours is a DOM question -- your transform can give you a tree,
but it doesn't address how you would plant it where you want it.
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list