We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

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

Medium Priority
295 Views
Last Modified: 2013-11-19
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
Comment
Watch Question

Carl TawnSenior Systems and Integration Developer
CERTIFIED EXPERT

Commented:
Can you post your existing XSL ? Or at least the part that deals with this section.

Commented:
What XSL processor are you using? I've never seen this behaviour before.

Author

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"/>
Commented:
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?

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Carl TawnSenior Systems and Integration Developer
CERTIFIED EXPERT
Commented:
<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 ?

Author

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.
Information Architect
CERTIFIED EXPERT
Top Expert 2006
Commented:
<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
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.