[Home] [By Thread] [By Date] [Recent Entries]
At 2012-07-09 13:25 -0500, russurquhart1@xxxxxxxxxxx wrote:
I have a couple of templates that i thought would handle things but they seem to be working wrong, but i know it must be something i am missing. Right ... because the second template is matching only elements named SubSection. You state "i have an element, in a SubSection", which means you have to match the child of SubSection. The match pattern "SubSection/*[@filter='filter1']" will match child elements of SubSection, other than another SubSection, that has the attribute. The first template, with the higher priority will catch those element children named SubSection. If you wanted to match any descendant element in a SubSection, then you would use the "SubSection//*[@filter='filter1']" pattern. It's getting matched in the third template. Shouldn't the first, second and third templates handle the possibilites? All three patterns you have match an element named SubSection ... not any element that is in a SubSection. I'm sure this is something i'm over looking, but i appreciate any help you can provide! I hope this helps. . . . . . . . . . . . . Ken -- Public XSLT, XSL-FO, UBL and code list classes in Europe -- Oct 2012 Contact us for world-wide XML consulting and instructor-led training Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/ G. Ken Holman mailto:gkholman@xxxxxxxxxxxxxxxxxxxx Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal
|

Cart



