XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Yitzhak KhabinskySubject: XSLT applied to entity encoded XML
Author: Yitzhak Khabinsky
Date: 15 Jun 2005 12:44 PM
Some portion of the input XML file is entity encoded, i.e. quotation marks and “less than” characters. So when I am applying XSLT to transform XML it fails when it touches entity encoded areas using statements like the following:
“xsl:value-of select=”…”

It seems that I need something like counterpart of the “disable-output-escaping”. Something like disable-INPUT-escaping on the input XML to remove entity encoding.

I attached sample XML and XSLT files.

Any thoughts?

Thank you in advance,
Yitzhak


UnknownYahoo.zip

Postnext
Ivan PedruzziSubject: XSLT applied to entity encoded XML
Author: Ivan Pedruzzi
Date: 16 Jun 2005 12:08 AM
Hi Yitzhak,

To solve this particular problem you have to use an extesion function.

The escaped text inside an element is not "markup" then can't be access using an Xpath expression.

The following solution uses saxon:parse , you need to run with saxon of course.

Hope this helps
Ivan Pedruzzi
Stylus Studio Team


<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:saxon="http://saxon.sf.net/">
<xsl:output indent="yes"/>
<xsl:template match="/">
<xsl:for-each select="root/Product">
<diamond>
<shape>
<xsl:variable name="dynamic" select="saxon:parse(Attributes)"/>
<xsl:value-of select="$dynamic/diamondAttr/@shape"/>
</shape>
<color>
<xsl:value-of select="Attributes/diamondAttr/@color"/>
</color>
</diamond>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>

Postnext
Yitzhak KhabinskySubject: XSLT applied to entity encoded XML
Author: Yitzhak Khabinsky
Date: 16 Jun 2005 08:23 PM
Hi Ivan,

Thanks for the idea.
I tried it and saxon:parse works like a charm.

Unfortunately, I can not use Saxon in my production environment.
We are using Microsoft .NET parser.

So I decided to build a XSLT extension in C#.
My idea for the implementation is to load my XML entity encoded string into XPathDocument and return back to the XSLT a node-set.
When I run it in the SS Enterprise Edition Build 377i it gives me an error. The error I am getting is easy reproduce with 2 files (XML and XSLT) in the attachment.


Thank you in advance,
Yitzhak


UnknownCSharpSaxon.zip

Postnext
Ivan PedruzziSubject: XSLT applied to entity encoded XML
Author: Ivan Pedruzzi
Date: 16 Jun 2005 11:02 PM

You just need to use the full class name for StringReader.
The following should work

Hope this Helps
Ivan Pedruzzi
Stylus Studio Team


XPathNodeIterator parse(String strXML)
{
System.IO.StringReader rdr = new System.IO.StringReader(strXML);
XPathDocument doc = new XPathDocument(rdr);
XPathNavigator nav = doc.CreateNavigator();

XPathExpression expr;
expr = nav.Compile("/");

XPathNodeIterator iterator = nav.Select(expr);

return iterator;
}

Postnext
Yitzhak KhabinskySubject: XSLT applied to entity encoded XML
Author: Yitzhak Khabinsky
Date: 17 Jun 2005 10:27 AM
Hi Ivan,

It works!!!

Two last things to take care:
1. While debugging, .NET processor doesn’t step into the extension function written in C#.
2. xmlns namespaces are being injected inside generated XML which spoils the entire XSLT transformation. How to prevent it from happening?

Thanks you in advance,
Yitzhak

Postnext
Ivan PedruzziSubject: XSLT applied to entity encoded XML
Author: Ivan Pedruzzi
Date: 17 Jun 2005 10:47 AM
Originally Posted: 17 Jun 2005 10:48 AM
1#: Unfortunately XslTranform doesn't provide a mechanism to do cross debugging

2#: To eliminate undesired prefix declarations use exclude-result-prefixes

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:ms="urn:schemas-microsoft-com:xslt"
xmlns:cs="urn:the-xml-files:xslt-csharp"
exclude-result-prefixes="cs ms">

Hope this helps
Ivan Pedruzzi
Stylus Studio Team

Postnext
Yitzhak KhabinskySubject: XSLT applied to entity encoded XML
Author: Yitzhak Khabinsky
Date: 17 Jun 2005 11:15 AM
Hi Ivan,

Thanks a lot for a great tech. support!

Regards,
Yitzhak

Postnext
Yitzhak KhabinskySubject: XSLT applied to entity encoded XML
Author: Yitzhak Khabinsky
Date: 17 Jun 2005 05:38 PM
Hi Ivan,

Thanks a lot for a great tech. support!

Regards,
Yitzhak

Postnext
ronny de deckerSubject: XSLT applied to entity encoded XML
Author: ronny de decker
Date: 19 Mar 2008 05:44 AM
Hi,

I wanted to execute your example because I am looking to use C#
in my xslt's.
Up to now I used Javascript, but I need C# functionality.

When I execute this Example of Yours in a simple tool Like Marrowsoft excelerator
I get an error message : "invalid class string"

In Stylus I get an somewhat more extended error message ( cfr. attachement )

I can not use C# for some reason or another, and I am working in Windows XP environment,I have visual studio 2005 installed.
What do I have to do to make this XSLT run, register certain dll's ?

Thanks in advance






>Hi Ivan,
>
>Thanks for the idea.
>I tried it and saxon:parse
>works like a charm.
>
>Unfortunately, I can not use
>Saxon in my production
>environment.
>We are using Microsoft .NET
>parser.
>
>So I decided to build a XSLT
>extension in C#.
>My idea for the implementation
>is to load my XML entity
>encoded string into
>XPathDocument and return back
>to the XSLT a node-set.
>When I run it in the SS
>Enterprise Edition Build 377i
>it gives me an error. The
>error I am getting is easy
>reproduce with 2 files (XML
>and XSLT) in the attachment.
>
>
>Thank you in advance,
>Yitzhak
>

Snapshot of error
ImageSaxon(1).bmp
snapshot

Postnext
Alberto MassariSubject: XSLT applied to entity encoded XML
Author: Alberto Massari
Date: 19 Mar 2008 06:23 AM
Ronny,
as Ivan wrote before, you should be using the full path:

System.IO.StringReader rdr = new System.IO.StringReader(strXML);

Alberto

Postnext
ronny de deckerSubject: XSLT applied to entity encoded XML
Author: ronny de decker
Date: 19 Mar 2008 06:37 AM
Thank You Alberto

for your Quick and helpfull reply.

I corrected as you said ...

and I was able to run the xslt in Stylus.

:-)

I am not able to run it in Marrowsoft XSelerator though,
has this to do with the fact I am using MSXML4.0 there?

Ronny


>Ronny,
>as Ivan wrote before, you
>should be using the full path:
>
>System.IO.StringReader rdr =
>new
>System.IO.StringReader(strXML)
>;
>
>Alberto

Postnext
Alberto MassariSubject: XSLT applied to entity encoded XML
Author: Alberto Massari
Date: 19 Mar 2008 06:58 AM
Hi Ronny,
this is a support forum for Stylus Studio, so I cannot tell you much about a different product; you should check with the publisher of XSelerator if they can run the .NET Xslt processor.

Alberto

Posttop
ronny de deckerSubject: XSLT applied to entity encoded XML
Author: ronny de decker
Date: 19 Mar 2008 07:02 AM
Thanks

;-)

I will buy Stylus

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.