Thank you again, Andrew.
Joe:I would very much like such a one - mostly to learn from, as I
think I will use the current solution. But I never know when this
might be handy. Thank you.
Regards,
Ragulf Pickaxe :-)
There are 3 ways I can think of to do this:
1- The way you are doing it now, pass the input xml in as a parameter
2- Use a custom URIResolver that intercepts a document() call and return
the input xml that way
3- Combine the two xml documents together before the transformation and
then the xslt only has to work on a single document.
Out of the 3, option 2 is the best but I'm not sure there's a .Net
equivalent of a custom URIResolver (which is in Java).
cheers
andrew
I can let you have a custom resolver I wrote for .NET if you need a head
start. You need to override XmlResolver.
Joe
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--