Mar 12, 2011 at 9:11 AM
Edited Mar 12, 2011 at 9:50 AM
1. referencing one XsltDb from another.
Tags like <mdo:*/> are not processed by XSLT processor. Those tags are used to split configuration in independent parts that can be executed separately. And then XSLT processor is executed.
As you noticed you can put XsltDb module as a user control inside another XsltDb module. In this case you will be able to use imported mdo:callable-s. But other stuff (mdo:service-s, mdo:template-s, mdo:importable-s etc.). won't work I think...
Actually, I must provide a way to explicitly reference configuration with out non-xslt tag like <mdo:import src="some other configuration"/>. But at the moment I have no such option.
2. Importing XSL dynamically.
You can't import external xsl on-the-fly, tis is an XSLT limitation. But you can
execute any xsl on-the-fly with mdo:transform(xml, xsl), or mdo:xsltdb(alias) extensions
<xsl:value-of select="'I am from external xsl 123'"/>
But at the moment these functions add some XsltDb-related extra output you probably don't want... I'll fix this in next release.