Extensions for external javascript files

[da...@mediagate.com]

As of December I used to call a set of libraries like this:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:lxslt="http://xml.apache.org/xslt"
xmlns:StringFunctions="C:/StringFunctions.xsl"
                extension-element-prefixes="StringFunctions"
                version="1.0">
...
</xsl:stylesheet>

The StringFunctions.xsl file looked like this:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:lxslt="http://xml.apache.org/xslt"
                xmlns:StringFunctions="commonFunctions"
                extension-element-prefixes="StringFunctions"
                version="1.0">
<xsl:output indent="yes" doctype-public="-//WAPFORUM//DTD WML 1.1//EN" doctype-system="http://www.wapforum.org/DTD/wml_1.1.xml"/>
<lxslt:component prefix="StringFunctions" functions="returnString URLEncodeString AddBreaksToTextMessage">
	<lxslt:script lang="javascript">
		function returnString(TheString)
		{
			return TheString;
		}
...
</lxslt:script>
</lxslt:component>
</xsl:stylesheet>

As of the most recent version of Xalan, my javascript extensions don't load anylonger.  Specifically, there is no error when the new namespace is declared, but the functions within the component do not seem to load nor work.

If I copy the extension component onto a stylesheet and change the namespace location, then the extension loads fine and all of the functions are available.


Has something changed that I'm not aware of?