Subject: Re: Trouble with XT?? From: Yann Desnoues <Yann.Desnoues@xxxxxxxxxx> Date: Thu, 16 Dec 1999 18:35:57 +0100 |
Thanks a lot, for you explanation, and comprehension for this "rookie question". I reread the specification and now I understand. I think that some people already said that the fact the call-template cannot take a "dynamic value" for name is "limiting". Could you kind enough to give me pointers about such kind of dicusssions (in this mailing list or elsewhere)? I wanted to do a filtering template that did some processing in some case and in any case call back the template I gave to him in parameter. To solve my trouble: I made a template (named dispatcher) which take the $v1 as a parameter and know all the possible value of $v1 (in order to redirect to the right template). (as you indicates me). Anyway... Thanks a lot. Yann Desnoues. David Carlisle wrote: > > <xsl:call-template name="$v1"/> <!-- this causes a trouble to XT --> > > You can't do that. The name has to be a `qname'. Variable values > are never qnames. The value of your $v1 in this case is a result tree > fragment consisting of a text node with value `called' that is not the > same as the name called. For similar reasons as > select="called" isn't the same as select="'called'". > > You have to do > <xsl:choose> > <xsl:when test="$v1='called'"> > <xsl:call-template name="called"/> > > So your input should cause trouble for any xsl processor. Yes. It should but it doesn't on LotusXSL (sometimes bugs can be useful). > > > David > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: Trouble with XT??, David Carlisle | Thread | Re: Trouble with XT??, David Carlisle |
RE: XSL sheet to output to a plain , Mike Brown | Date | RE: Mozilla Support for XSL XSLT? Y, disco |
Month |