Copy entire XML except, but change a few nodes...

samjudson · March 16th, 2011, 01:56 PM

Your original post contains a sample of XML called "desired output". This doesn't contain an <outputfile> element, so we're not sure where that came from, nor how you want it to be output.

Try restating your requirements.

Martin Honnen · March 16th, 2011, 02:02 PM

Use the two templates Michael Kay suggested, then to output the "outputfile" element as the first child element of the root element add a template

Code:

<xsl:template match="/*">
  <xsl:copy>
    <xsl:apply-templates select="@*"/>
    <outputfile><xsl:value-of select="$vLeague_Name"/>_CLIENT_SAMPLE.XML</outputfile>
  </xsl:copy>
</xsl:template>

If you want to output the "outputfile" element before the root element then you need

Code:

<xsl:template match="/">
  <outputfile><xsl:value-of select="$vLeague_Name"/>_CLIENT_SAMPLE.XML</outputfile>
  <xsl:apply-templates/>
</xsl:template>

instead, but take notice that that way you don't get a well-formed XML result document as you can't have two root elements.

vb89 · March 16th, 2011, 02:04 PM

Sam,
I've edited my XSL code (posted earlier) to reflect the names of the XML that i posted in my original post.

In regards the outputfile element, that's something used by the XT processor to rename the new file.

Martin Honnen · March 16th, 2011, 02:16 PM

Quote:

Originally Posted by vb89

Martin,
XT is an implementation in Java of XSL Transformations (http://www.jclark.com/xml/xt-old.html)

I wouldn't use XT, if you use Java then use a conforming implementation like Saxon 6.5.5 for XSLT 1.0 or like Saxon 9 for XSLT 2.0. If you look at the document you linked to it lists some limitations and one of them is "The node() node-test does not work in match patterns" so you simply run into that problem because you use some beta release of an old software.

vb89 · March 16th, 2011, 02:20 PM

Thanks Martin.

Unfortunately, this is what we use in our production environment -- dumb, i know. Is there a work around that you can think of?

mhkay · March 16th, 2011, 02:58 PM

If you know that something is dumb then stop doing it.

Building a production system on xt is not just dumb, its insane. The product was never finished, and development stopped over 10 years ago, and there are excellent alternatives.

vb89 · March 16th, 2011, 03:08 PM

Michael, I understand where you're coming from -- for the record we're also using NXSLT (not sure if that helps). However, for the project at hand these are the circumstances that I'm forced to deal with, so I have to adjust to them and work with what I got. If you have any thoughts on a work around, I would appreciate it, if not, I'll have to just continue searching.

Martin Honnen · March 16th, 2011, 03:26 PM

If you can't do match="node()" then you have to spell out the different node types i.e.

Code:

<xsl:template match="@* | text() | comment() | processing-instruction()">
  <xsl:copy/>
</xsl:template>

<xsl:template match="*">
  <xsl:copy>
    <xsl:apply-templates select="@* | node()"/>
  </xsl:copy>
</xsl:template>

then you need to add other templates below and perhaps use priority to make sure they have higher priority than match="*".

But I would also strongly suggest to change the system to use a conforming XSLT processor and not to rely on workarounds to adapt to some old software.