Re: [xsl] [ERR XTSE0210] when importing a stylesheet indirectly

Subject: Re: [xsl] [ERR XTSE0210] when importing a stylesheet indirectly
From: Johannes Neubauer <johannes.neubauer@xxxxxxxxxxxxxxxxx>
Date: Fri, 29 Feb 2008 12:46:17 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ronan Klyne schrieb:
|> Oh, that's a behaviour I didn't expect. Why don't you look at the key
|> definition and if there already is a key definition with that name, use
|> and match attributes, no new index is created? Will you change this in
|> future releases?
|
| This is a useful feature - you can use two <xsl:key > elements to
| instruct the processor to put two different sets of nodes and values
| into the same index.

Yes, but then the use or match attributes aren't the same. I meant
xsl:keys that are duplicates, so you have to xsl:key definitions,
defining the same index (perhaps because it is in a module that is
imported multiple times). You mean several key definitions with the same
name, but indexing different nodes, aren't you? This is part of the spec
and shouldn't be changed, I agree. But my question was about redundant
key definitions.

wfg,
Jonny.

|     # r
|
|
|
|
|

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHx/CJGaEJacf6i/cRAqQ4AJ4kMFojcqlWjxrLx+LSEyhWd8hPywCglLOh
WPgPLG28RiT3erZhOvW7dPI=
=yjX6
-----END PGP SIGNATURE-----

Current Thread