This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cascading for name templates vs match templates


Hello Mattias,

I gather from your error, that it's exactly the problem Stuart 
describes. You have to change your <xsl:include>s to <xsl:import>s "and 
everything will be ok then" ;-)

Joerg

Stuart Celarier schrieb:
> Mattias, you didn't really specify if you are using <xsl:include> or
> <xsl:import>. They are quite different. For reference, see the XSLT 1.0
> spec http://www.w3.org/TR/xslt#section-Combining-Stylesheets.
> 
> What you describe sound possible, and it sounds like you'd like to be
> using <xsl:import>. Check out <xsl:import> and <xsl:include> in the spec
> or any XSLT textbook. If this doesn't solve your problem, please post a
> brief, minimal example of your problem and include the name of the XSLT
> processor you are using.
> 
> Cheers,
> Stuart
> 
> -----Original Message-----
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com] On Behalf Of Mattias
> Konradsson
>  
> When you include stylesheets containing templates matching the same
> elements
> they're cascaded in the order they're added and the templates actually
> defined in the stylesheet taking priority, but this doesn't seem true
> for
> template with name attributes where I'm getting an "duplicit name" error
> when including stylesheets that has the same name as another. I'd really
> like this to work like match templates so I can "inherit" templates if
> they
> exist, is there any way to do that or is it just the way it is?


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]