I found setMessageEmitterClass() in the Configuration object, but it’s rather inconvenient in that it takes the NAME of the emitter class, preventing me from instantiating an instance in advance with, for example, the logging object I want to use to log the messages.  Is there a way to set the emitter with an object instance instead of a class name?


From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of Michael Kay
Sent: Wednesday, January 16, 2008 4:25 PM
To: 'Mailing list for SAXON XSLT queries'
Subject: Re: [saxon] Transformer.setErrorListener() and <xsl:message...>


Saxon allows you to call setMessageEmitter() to register a listener for the output of xsl:message. Typically you can subclass the standard MessageEmitter. This mechanism was introduced before JAXP introduced the idea of sending message output to the ErrorListener, a feature which I never implemented because I couldn't see how to do it without breaking existing applications.


Michael Kay



From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of Jim Garrison
Sent: 16 January 2008 21:49
To: saxon-help@lists.sourceforge.net
Subject: [saxon] Transformer.setErrorListener() and <xsl:message...>

Does Saxon B9 allow capturing the text of <xsl:message…> tags?


I tried attaching an ErrorListener to the Transformer with setErrorListener(), but the listener’s methods are not invoked for <xsl:message>, with or without terminate=”yes”.