(You should always feel free to ask Xalan questions on either the [EMAIL PROTECTED] mailing list, for general questions like this one, or the [email protected] list for advanced API issues. Since Xalan committers are all volunteers, you're not guaranteed responses to individuals' email addresses)
----You <[EMAIL PROTECTED]> wrote:---- I have a question related to this issue that you helped me with several months back. At the top of my template I declare the xalan for the Meta tag issue. But then I am also doing an Xalan:evaluate on the template. The transformer complains at this point since Xalan is defined already. Any thoughts? <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version="1.0" xmlns:xalan="http://xml.apache.org/xslt"; xmlns:xalan="http://xml.apache.org/xalan"; exclude-result-prefixes="xalan"> ---- Of course this is an error, you're not allowed to redefine namespaces xmlns:xalan like that (well, as far as I know). One is incorrect... and today is too much of a Monday for me to tell you which one. Volunteers? I just grepped our sources and there are plenty of instances of both ...org/xalan and ...org/xslt, and I'm trying to remember why the heck we have two different URNs/namespaces. Does someone want to remind me? The quick answer is that you need to either define the namespaces closer to where you're using them - i.e. in the elements where you need them. Or, you can simply declare one to be xalanfeature and the other to be xalan - the actual part of the name next to the xmlns: really doesn't mean anything, as long as it matches what it's being referenced by. I.e. I think you want to keep xmlns:xalan="http://xml.apache.org/xalan";, and then have another decl like xmlns:xalan-output-features ="http://xml.apache.org/xslt";, and use the second one in your xsl:output tag for the Xalan-custom feature to omit the META tag. Am I making any sense? - Shane
