xsl script removing closing tag name and replacing with </>

Hello folks,

Here is an example of my xml file BEFORE running through xsl script:

<root>
   <Image1>img/image1.gif</Image1>
   <Image2>img/image2.gif</Image2>
   <Image3>img/image3.gif</Image3>
<root>

Here is the xml file AFTER running though xsl script:

<root>
   <Image1>img/image1.gif</>
   <Image2>img/image2.gif</>
   <Image3>img/image3.gif</>
<root>

I do not want the end tags to be replaced with </>.  Does anybody know how to force the script to leave as is?

Thanks
LVL 1
nothing8171Asked:
Who is Participating?
 
Geert BormansInformation ArchitectCommented:
<test></test> and <test /> are equivalent
and you can't tell an XSLT processor to choose either form for empty elements
it is just a syntax difference of no value

you have a good usecase though for being able to add an endtag

what I usually do to force an endtag is just create an comment tag in it
such as <!-- EMPTY -->
You can then easily get rid of that using SED or AWK, PYTHON,....

doing so, I once discovered something that only works in Xalan (it did for me in Xalan for Java)
but that can be helpful for you
create a comment inside a parameter (global one) like this
    <xsl:param name="empty"><xsl:comment>EMPTY</xsl:comment></xsl:param>
then use that parameter, like this
            <text><xsl:value-of select="$empty"/></text>
you would expect to get this
<text><!-- EMPTY --></text>
instead you get this in Xalan
<text></text>
and this in Saxon
<text/>

so you can't rely on this to go well each time,
but for this once and since you are using Xalan
you might as well be lucky
call it an undocumented feature :-)

cheers

Geert
0
 
Carl TawnSystems and Integration DeveloperCommented:
Can you post your existing XSL ? Or at least the part that deals with this section.
0
 
pvginkelCommented:
What XSL processor are you using? I've never seen this behaviour before.
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

 
nothing8171Author Commented:
XML BEFORE
<Something x="some_data"
                  y="other_data">
</Something>

XSL SCRIPT
<xsl:template match="Something">
    <xsl:copy>
      <xsl:copy-of select="@x"/>
      <xsl:copy-of select="@y"/>
    </xsl:copy>
  </xsl:template>

XML AFTER
<Something x="some_data"
                  y="other_data"/>
0
 
pvginkelCommented:
The last example is what is to be expected. I don't think this is something you can get around. What script creates the code in your question and what processor are you using?
0
 
Carl TawnSystems and Integration DeveloperCommented:
<Something x="some_data" y="other_data"/>

is perfectly valid, and is just a shorthand for:

<Something x="some_data" y="other_data">
</Something>

Whereas the snippet you posted earlier actually had the closing Image tag missing which would invalidate the XML. Is this what is happening, or was your original version a typo ?
0
 
nothing8171Author Commented:
The XSL processor is "Xalan" and I realize this is acceptable, but I am comparing thousands of old files with new files.  The old files have the </Something> and the new ones only </>.  It's an annoyance when performing diffs.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.