Re: xsl:message support

Wendell,

Why not using xsl:result-document and create a sequence that you could get
out of the p:xslt step ?

Xmlizer

2012/4/3 Wendell Piez <wapiez@mulberrytech.com>

> Dear Vojtech and xproc-dev,
>
>
> On 4/3/2012 2:29 AM, vojtech.toman@emc.com 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:
>> http://www.w3.org/TR/xproc/#**error-example<http://www.w3.org/TR/xproc/#error-example>,
>> or in this XProc test: http://tests.xproc.org/tests/**
>> required/try-003.xml <http://tests.xproc.org/tests/required/try-003.xml>
>>
>
> 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                            mailto:wapiez@mulberrytech.com
> Mulberry Technologies, Inc.                http://www.mulberrytech.com
> 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
> ==============================**==============================**==========
>
>