[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Multiple/conditional import problem

Subject: Re: Multiple/conditional import problem
From: Martynas Jusevicius <martynas.jusevicius@xxxxxxxxx>
Date: Thu, 26 May 2011 16:31:46 +0200
Re:  Multiple/conditional import problem
Thanks again! It helps me to see the picture - it's not as trivial as
I expected...

Wouldn't <xsl:import> (with a subsiduary stylesheet) make more sense
than <xsl:include>? I could call them master.xsl and default.xsl for
example. Then I wouldn't need to care about template clashes, which is
totally possible if I don't control the imported stylesheets.

> the only problem is that then your default template for property/vale will
> always win as import precedence trumps priority.
> So use xsl:include rather than  xsl:import
>
> If you do want to use xsl:import keep your general framework in the top
> stylesheet but put your default templates such as
>> <xsl:template match="property/value">
>>    <xsl:value-of select="."/>
>> </xsltemplate>
>>
> into a subsidurary stylesheet that is imported last so has lower import
> precedence than your property-specific styles,

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.