This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: using default params?
David Carlisle <davidc@nag.co.uk> writes:
> > What I'm looking for is something like being able to
>
> > <xsl:param name="a_name" select="eval(@a_name or 'default_value')"/>
>
> <xsl:param name="a_name">
> <xsl:choose>
> <xsl:when test="@a_name"><xsl:value-of select="@_name"/></xsl:when>
> <xsl:otherwise>default</xsl:otherwise>
> </xsl:choose>
> </xsl:param>
>
> does what you say you are looking for, but it's not what you want.
Indeed... but basically it's not what I want becuse of the fact that
in my real world case (not the stupid little example) I want to pass
upt to 7,8 parameters.... the syntax
choose-when-/when-otherwise-/otherwise-/choose is more than a little
bit stupid for this...
> what you want is
>
> <table bgcolor="#ff0000">
> <xsl:if test="@col1"><xsl:value-of select="@col1"/></xsl:if>
> <tr><td><xsl:apply-templates/></td></tr>
> <table>
this I don't understand. what if I want to do something like
<table bgcolor="#ff0000" border="1"> and have both overridden?
> if your input attribute had had the same name as the result attribute
> it is simpler
>
> <table bgcolor="#ff0000">
> <xsl:copy-of select="@bgcolor"/>
> <tr><td><xsl:apply-templates/></td></tr>
> <table>
>
And I don't understand this, too :-(
why don't you need a test for existence in this example around the
xsl:copy-of ?
thank you very much so far,
jtl
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list