|
|
You're in the
dotnet xml
group:is this stylesheet valid?
dotnet xml:
i'm porting some xsl code from .net 1.1 to 2.0 and I have come across a transform which works in .net 1.1 and works in mxsml but does not work in ..net 2.0. the stylesheet is this: <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="foo"> <xsl:param name="param1"/> <xsl:value-of select="$param1/*"/> <xsl:apply-templates/> </xsl:template> </xsl:stylesheet> and the input file is simply <foo /> so $param1 has no value (empty string? empty node set? I'm not sure) with .net 2.0 I get an error message Unhandled Exception: System.Xml.XPath.XPathException: Expression must evaluate to a node-set. I'm guessing this is because the default parameter value is an empty string. in the real stylesheet, the parameter (if it is passed in) will be a node set. so to make sure I don't evaluate an illegal expression, I need to be able to tell whether the parameter value is an empty string (i.e. default) or a node set. how can I achieve this? Andy
* Andy Fish wrote in microsoft.public.dotnet.xml:
[quoted text, click to view] > <xsl:param name="param1"/> > <xsl:value-of select="$param1/*"/> >in the real stylesheet, the parameter (if it is passed in) will be a node >set. so to make sure I don't evaluate an illegal expression, I need to be >able to tell whether the parameter value is an empty string (i.e. default) >or a node set. how can I achieve this? You could simply check whether $param1 evaluates to a true value, e.g. <xsl:if text='$param1'> <xsl:value-of select="$param1/*"/> </xsl:if> should do. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
[quoted text, click to view]
Andy Fish wrote: > i'm porting some xsl code from .net 1.1 to 2.0 and I have come across a > transform which works in .net 1.1 and works in mxsml but does not work in > .net 2.0. the stylesheet is this: > > <?xml version="1.0" encoding="UTF-8"?> > <xsl:stylesheet version="1.0" > xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> > <xsl:template match="foo"> > <xsl:param name="param1"/> > <xsl:value-of select="$param1/*"/> > <xsl:apply-templates/> > </xsl:template> > </xsl:stylesheet> > > and the input file is simply > > <foo /> > > so $param1 has no value (empty string? empty node set? I'm not sure) > > with .net 2.0 I get an error message Unhandled Exception: > System.Xml.XPath.XPathException: Expression must evaluate to a node-set. I'm > guessing this is because the default parameter value is an empty string. If I understand <http://www.w3.org/TR/xslt#variable-values> correctly then the default value is the empty string. [quoted text, click to view] > in the real stylesheet, the parameter (if it is passed in) will be a node > set. so to make sure I don't evaluate an illegal expression, I need to be > able to tell whether the parameter value is an empty string (i.e. default) > or a node set. how can I achieve this? To avoid the exception it should suffice to set <xsl:param name="param1" select="/.."/> as that way the value is an empty node set and then <xsl:value-of select="$param1/*"/> does not give an exception. -- Martin Honnen --- MVP XML
[quoted text, click to view]
Andy Fish wrote: > hi, > > i'm porting some xsl code from .net 1.1 to 2.0 and I have come across a > transform which works in .net 1.1 and works in mxsml but does not work in > .net 2.0. the stylesheet is this: > > <?xml version="1.0" encoding="UTF-8"?> > <xsl:stylesheet version="1.0" > xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> > <xsl:template match="foo"> > <xsl:param name="param1"/> > <xsl:value-of select="$param1/*"/> > <xsl:apply-templates/> > </xsl:template> > </xsl:stylesheet> > > and the input file is simply > > <foo /> > > so $param1 has no value (empty string? empty node set? I'm not sure) > > with .net 2.0 I get an error message Unhandled Exception: > System.Xml.XPath.XPathException: Expression must evaluate to a node-set. I'm > guessing this is because the default parameter value is an empty string. > > in the real stylesheet, the parameter (if it is passed in) will be a node > set. so to make sure I don't evaluate an illegal expression, I need to be > able to tell whether the parameter value is an empty string (i.e. default) > or a node set. how can I achieve this? > > Andy > > rather than have it default to an empty string, and then having to test for that to avoid using the variable in path expressions, it's usually simpler just to make it default to an empty node set, add <xsl:param name="param1" select="/.."/> David --
[quoted text, click to view] "David Carlisle" <david-news@dcarlisle.demon.co.uk> wrote in message news:46608917.2000608@dcarlisle.demon.co.uk... > Andy Fish wrote: >> hi, >> >> i'm porting some xsl code from .net 1.1 to 2.0 and I have come across a >> transform which works in .net 1.1 and works in mxsml but does not work in >> .net 2.0. the stylesheet is this: >> >> <?xml version="1.0" encoding="UTF-8"?> >> <xsl:stylesheet version="1.0" >> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> >> <xsl:template match="foo"> >> <xsl:param name="param1"/> >> <xsl:value-of select="$param1/*"/> >> <xsl:apply-templates/> >> </xsl:template> >> </xsl:stylesheet> >> >> and the input file is simply >> >> <foo /> >> >> so $param1 has no value (empty string? empty node set? I'm not sure) >> >> with .net 2.0 I get an error message Unhandled Exception: >> System.Xml.XPath.XPathException: Expression must evaluate to a node-set. >> I'm guessing this is because the default parameter value is an empty >> string. >> >> in the real stylesheet, the parameter (if it is passed in) will be a node >> set. so to make sure I don't evaluate an illegal expression, I need to be >> able to tell whether the parameter value is an empty string (i.e. >> default) or a node set. how can I achieve this? >> >> Andy >> >> > > > rather than have it default to an empty string, and then having to test > for that to avoid using the variable in path expressions, it's usually > simpler just to make it default to an empty node set, add > <xsl:param name="param1" select="/.."/> > > David > > > -- > http://dpcarlisle.blogspot.com Thanks david, that's pretty much what I ended up doing unfortunately there were quite a lot of templates with this optional parameter, although only one of them actually used the parameter. they are calling each other like this: <xsl:template match="..."> <xsl:param name="param1"/> .... <xsl:apply-templates> <xsl: with-param name="param1" select="$param1"> </xsl:template> </xsl:apply-templates/> </xsl:template > now, if any one of them gets called without a parameter, it passes in the blank parameter into the ones it calls (rather than not passing in a parameter - hence the default value does not apply), so this meant I had to put the default parameter into every one of the templates, not just the one that needed it. so as well as some way of telling whether a variable contains a node set, string or RTF, I would also like to have an option on <xsl:call-template> and <xsl:apply template> that said: if this parameter was passed in to me, pass the parameter into the next template,. otherwise don't pass in the parameter into the next template Andy
Andy Fish <ajfish@blueyonder.co.uk> wrote in <Vqb9i.31422$Ro3.15173@text.news.blueyonder.co.uk>: [quoted text, click to view] > "David Carlisle" <david-news@dcarlisle.demon.co.uk> wrote > in message news:46608917.2000608@dcarlisle.demon.co.uk... >> Andy Fish wrote: >>> so $param1 has no value (empty string? empty node set? >>> I'm not sure) >> >> rather than have it default to an empty string, and then >> having to test for that to avoid using the variable in >> path expressions, it's usually simpler just to make it >> default to an empty node set, add <xsl:param >> name="param1" select="/.."/> > > unfortunately there were quite a lot of templates with > this optional parameter, although only one of them > actually used the parameter. [...] [quoted text, click to view] > so as well as some way of telling whether a variable > contains a node set, string or RTF, I would also like to > have an option on <xsl:call-template> and <xsl:apply > template> that said: > > if this parameter was passed in to me, pass the parameter > into the next template,. otherwise don't pass in the > parameter into the next template Read XSLT2 spec, 10.1.2 and rejoice. (Although I must say I don't see how precisely that would help you, since from the description of your predicament it would seem you'd have to specify the tunneling everywhere anyway.) --
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |