I'd suggest using the approach taken in FXSL and used successfully for
many years. As an added benefit your code will not depend on a single
XSLT processor implementation.
For more information read:
http://conferences.idealliance.org/extreme/html/2006/Novatchev01/EML2006Novatchev01.html
--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play
On Thu, Jul 22, 2010 at 10:29 AM, Bill French <french(_at_)recommind(_dot_)com>
wrote:
Hi all,
Let's just say I were using saxon:call-template to call templates whose
names weren't known until runtime. Is there a way to catch the error that
results if the template doesn't exist? I haven't found any way to do this.
Using Saxon 9.1.0.8, Java.
Regards,
--Bill
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--