There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.
Solved
XSL - using CDATA or other to escape message otherwise seen as markup
Posted on 2013-06-25
I'm trying to use CDATA to escape a block of text that would otherwise be interpreted as markup.
I have the following .xsl
<xsl:template match="Response">
<Request>
MI
<xsl:call-template name="strip-between-tags">
<xsl:with-param name="str" select="."/>
</xsl:call-template>
</Request>
</xsl:template>
<xsl:template name="strip-between-tags">
<xsl:param name="str"/>
<xsl:if test="contains($str, '<')">
<xsl:text disable-output-escaping="y
<xsl:value-of select="substring-before(s
<xsl:text disable-output-escaping="y
<xsl:call-template name="strip-between-tags">
<xsl:with-param name="str" select="substring-after($s
</xsl:call-template>
</xsl:if>
<xsl:if test="not (contains($str, '<'))">
<xsl:text disable-output-escaping="y
</xsl:if>
</xsl:template>
This is my input data that I'm feeding into the xsl:
<CommandRS Version="2003.XML1.0.1">
<Response>MI<X> X IF SELECT NAME <CAD>< ></Response>
</CommandRS>
Produces output
<CommandRQ Version="2003.XML.0.1">
<Request>MI<X><CAD>< > <X> </Request>
</CommandRQ>
However, the output is erroring out because of the message between the Request tags.
So I tried changing my xsl to include CDATA:
<xsl:template match="Response">
<Request>
<![CDATA[
MI
<xsl:call-template name="strip-between-tags">
<xsl:with-param name="str" select="."/>
</xsl:call-template>
]]>
</Request>
</xsl:template>
but this would comment out my template call. Please advise on how I can escape the block of text using CDATA or other method.
I also tried
<xsl:template match="Response">
<Request>
<xsl:text><![CDATA[ ]]></xsl:text>
MI
<xsl:call-template name="strip-between-tags">
<xsl:with-param name="str" select="."/>
</xsl:call-template>
</Request>
</xsl:template>
but the output never included the "![CDATA[". Not sure how to implement this into the xsl
I have the following .xsl
<xsl:template match="Response">
<Request>
MI
<xsl:call-template name="strip-between-tags">
<xsl:with-param name="str" select="."/>
</xsl:call-template>
</Request>
</xsl:template>
<xsl:template name="strip-between-tags">
<xsl:param name="str"/>
<xsl:if test="contains($str, '<')">
<xsl:text disable-output-escaping="y
<xsl:value-of select="substring-before(s
<xsl:text disable-output-escaping="y
<xsl:call-template name="strip-between-tags">
<xsl:with-param name="str" select="substring-after($s
</xsl:call-template>
</xsl:if>
<xsl:if test="not (contains($str, '<'))">
<xsl:text disable-output-escaping="y
</xsl:if>
</xsl:template>
This is my input data that I'm feeding into the xsl:
<CommandRS Version="2003.XML1.0.1">
<Response>MI<X> X IF SELECT NAME <CAD>< ></Response>
</CommandRS>
Produces output
<CommandRQ Version="2003.XML.0.1">
<Request>MI<X><CAD>< > <X> </Request>
</CommandRQ>
However, the output is erroring out because of the message between the Request tags.
So I tried changing my xsl to include CDATA:
<xsl:template match="Response">
<Request>
<![CDATA[
MI
<xsl:call-template name="strip-between-tags">
<xsl:with-param name="str" select="."/>
</xsl:call-template>
]]>
</Request>
</xsl:template>
but this would comment out my template call. Please advise on how I can escape the block of text using CDATA or other method.
I also tried
<xsl:template match="Response">
<Request>
<xsl:text><![CDATA[ ]]></xsl:text>
MI
<xsl:call-template name="strip-between-tags">
<xsl:with-param name="str" select="."/>
</xsl:call-template>
</Request>
</xsl:template>
but the output never included the "
3-
3
2
8 Comments
Active 3 days ago
Never tried that, but may be the "cdata-section-elements" attribute of the xsl:output element might help?
<xsl:output method="xml" cdata-section-elements="Re
<xsl:output method="xml" cdata-section-elements="Re
zc2:
how do you incorporate that. i just added that line in my <xsl:template match="Response"> but it didn't like it.
how do you incorporate that. i just added that line in my <xsl:template match="Response"> but it didn't like it.
Active 1 day ago
it is on the xsl:output you need to put that, have done that a lot, works well
<xsl:output indent="yes" cdata-section-elements="Re
(note: xsl:output is a top level element in case you haven't used it)
the result element is what you need to put there
but you also need to remove the disable-output-escaping if you do that
<xsl:text disable-output-escaping="y
should be
<xsl:text>></xsl:text>
<xsl:output indent="yes" cdata-section-elements="Re
(note: xsl:output is a top level element in case you haven't used it)
the result element is what you need to put there
but you also need to remove the disable-output-escaping if you do that
<xsl:text disable-output-escaping="y
should be
<xsl:text>></xsl:text>
Active 3 days ago
Put this xsl:output line right after the first root element's opening tag of the XSLT:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output indent="yes" cdata-section-elements="Request"/>
what's the diff between
<xsl:output method="xml" cdata-section-elements="Re
and
<xsl:output indent="yes" cdata-section-elements="Re
method versus indent?
<xsl:output method="xml" cdata-section-elements="Re
and
<xsl:output indent="yes" cdata-section-elements="Re
method versus indent?
Active 1 day ago
method says you are creating XML, but that is the default if you output a root element different from <html>, so not really required
indent=yes makes that the output is indented (so easier to view)
it is all different attributes to the output element
the output element organises teh serialisation
In this stylesheet
<xsl:output method="xml" indent="yes" cdata-section-elements="Re
would be equivalent to
<xsl:output indent="yes" cdata-section-elements="Re
indent=yes makes that the output is indented (so easier to view)
it is all different attributes to the output element
the output element organises teh serialisation
In this stylesheet
<xsl:output method="xml" indent="yes" cdata-section-elements="Re
would be equivalent to
<xsl:output indent="yes" cdata-section-elements="Re
There was no need for me to remove the disable-output-escaping when i added <xsl:output indent="yes" cdata-section-elements="Re
I saw same output.
I saw same output.
Active 1 day ago
mmh, I have do disagree with that last statement.
If you see no difference with msxml, then that means msxml does it wrong.
Saxon does it right, there is a little quirk in Xalan too
if you tell the serialiser to make an element having CDATA content, you tell it to put all text nodes in a CDATA section.
BUT... by setting the d-o-e to yes, you tell the serialiser NOT to escape the '<' on output. Essentialy that means that you are outputting a STAGO (start tag opener), not a '<' character. That is not text, so should not be treated as text and the CDATA section should stop before and restart after the '<'. Most processors do that right. I also tested msxml, and it does the wrong thing. But this really is in the grey areas of XSLT.
However, I see no reason why you would leave an erroneous construct in your stylesheet. It makes your stylesheet less portable and unpredictable.
For msxml there is no difference. But I suggest you get rid of the d-o-e in your stylesheet. It would then also do the right thing with other processors
If you see no difference with msxml, then that means msxml does it wrong.
Saxon does it right, there is a little quirk in Xalan too
if you tell the serialiser to make an element having CDATA content, you tell it to put all text nodes in a CDATA section.
BUT... by setting the d-o-e to yes, you tell the serialiser NOT to escape the '<' on output. Essentialy that means that you are outputting a STAGO (start tag opener), not a '<' character. That is not text, so should not be treated as text and the CDATA section should stop before and restart after the '<'. Most processors do that right. I also tested msxml, and it does the wrong thing. But this really is in the grey areas of XSLT.
However, I see no reason why you would leave an erroneous construct in your stylesheet. It makes your stylesheet less portable and unpredictable.
For msxml there is no difference. But I suggest you get rid of the d-o-e in your stylesheet. It would then also do the right thing with other processors
Featured Post
Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.
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.
Join & Write a Comment Already a member? Login.
Introduction
A frequently asked question goes something like this: "I am running a long process in the background and I want to alert my client when the process finishes. How can I send a message to the browser?" Unfortunately, the short answer…
- CSS
- HTML
- JavaScript
- PHP
- jQuery
- AJAX
So you have coded your own WordPress plugin and now you want to allow users to upload images to a folder in the plugin folder rather than the default media location? Follow along and this article will show you how to do just that!
In this tutorial viewers will learn how to style transparent/translucent elements using alpha transparency in CSS
Start with a normal styled element, such as a div.: Define its "background-color" property as "rgba (255, 255, 255, .5): The numbers in…
In this tutorial viewers will learn how to style a corner ribbon overlay for an image using CSS
Create a new class by typing ".Ribbon": Define the class' "display:" as "inline-block": Define its "position:" as "relative": Define its "overflow:" as …
Suggested Courses
Course of the Month5 days, 2 hours left to enroll
580 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.