Re: [xsl] match on attribute anywhere

[Wendell Piez <wapiez at mulberrytech dot com>]

That's all true, Trevor.

Possibly we don't think of this since xsl:apply-imports is rare enough 
we're not tuned into it as being effectively an inheritance mechanism (and 
useful as such).

On the other hand, maybe now we will be.

Yet it's typical of XSL-List that we've seen four decent solutions to this 
problem already today (conditional logic, modes, matching the attribute, 
and using xsl:apply-imports), and learned something while we were at it.

Cheers,
Wendell

At 03:03 PM 2/14/02, you wrote:
>This is really a very old pattern but in a new context.  In
>object-oriented languages it is common to write a class which inherits
>from another, overrides a method (or two), do some new stuff, then
>call the base version of the same method to do what the base class
>does.
>
>Which is why I've been kicking myself for not thinking of the
>apply-imports method first - I've been using OOPLs a lot of years, and
>well know the correspondence between XSLT import and inheritance.  Oh
>well.
>
>The interesting thing XSLT has over OOPLs in general is that since the
>method name is essentially the template match pattern you get to
>overide many "methods" (templates) at once, as in the *[@mark] trick.
>A new feature for Java 3 maybe...


======================================================================
Wendell Piez                            mailto:wapiez@mulberrytech.com
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


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