Re: xsl:message support

As far as I remember, at some point the implementation of p:xslt in Calabash used to dispatch xsl:message[not(@terminate)] to its internal MessageListener, the default implementation of which writes to the standard output stream. I can't tell if this is still the case though, but if it wasn't one could always override the implementation of the p:xslt step to log messages and simply declare this custom implementation using the Calabash configuration mechanisms.


On 3 avr. 2012, at 17:56, Wendell Piez wrote:

> Dear Vojtech and xproc-dev,
> On 4/3/2012 2:29 AM, wrote:
>> Currently, the only standard way to get the results of xsl:message is using the p:try/p:catch step. This, however, works only in the cases when you use<xsl:message terminate="yes">. Without terminate set to "yes", you cannot access the messages.
>> You can find an example of this in the XProc specification:, or in this XProc test:
> Thanks, this is very useful info.
> We may end up dropping our messages in as XML and then filtering them into a separate "warnings" pipe. I imagine this is being done a fair amount: is it more or less the recommendation when developers want to use xsl:message to emit runtime warnings? Are there other ideas I have missed?
> Cheers,
> Wendell
> -- 
> ======================================================================
> Wendell Piez                  
> Mulberry Technologies, Inc.      
> 17 West Jefferson Street                    Direct Phone: 301/315-9635
> Suite 207                                          Phone: 301/315-9631
> Rockville, MD  20850                                 Fax: 301/315-8285
> ----------------------------------------------------------------------
>  Mulberry Technologies: A Consultancy Specializing in SGML and XML
> ======================================================================

Received on Tuesday, 3 April 2012 18:35:54 UTC