If I'm not mistaken, the above change shouldn't make any difference to a namespace-aware XML application; no element is in a different namespace than it was before. Nevertheless this seems to be making a crucial difference to the logicsheet processor.
Yes, same opinion here.
Am I missing something, or is this indeed a bug?
I would call it a bug. Please add it to Bugzilla - and provide a patch if you can :)
P.S. The logicsheet begins like this:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; xmlns:xsp="http://apache.org/xsp"; xmlns:sil="http://www.sil.org/namespace/xsp-query"; xmlns:esql="http://apache.org/cocoon/SQL/v2";>
<xsl:output indent="yes" method="xml" />
<xsl:template match="sil:query">
so this template should match any <sil:query> that's in the right namespace, regardless of whether the namespace declaration occurs on the <sil:query> element itself, or an ancestor. (In fact the XSL processor shouldn't even know the difference!)
I don't think the transformation itself fails - it's not even called. It's a problem of Cocoon itself, but don't ask me about internals.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
