You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2014/08/27 13:42:58 UTC

[jira] [Commented] (CAMEL-7753) xslt component - Store warning/errors etc as exchange properties so end users can get hold of those

    [ https://issues.apache.org/jira/browse/CAMEL-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112162#comment-14112162 ] 

Claus Ibsen commented on CAMEL-7753:
------------------------------------

Saxon is a bit special, so we need to do some special code to hook it into use the jaxp error listener for xslt messages.
https://stackoverflow.com/questions/4695489/capture-xslmessage-output-in-java

> xslt component - Store warning/errors etc as exchange properties so end users can get hold of those
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7753
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7753
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.14.0
>
>
> If you use xslt:message to output an error and terminate the xslt processing, then you cannot get hold of the message, just some generic exception about xslt terminated.
> We should capture those warnings/error/fatal error messages the listener emits and store on exchange so end users can get hold of those details.
> An example
> http://www.w3schools.com/xsl/el_message.asp
> We should be able to get that artist is empty text message.



--
This message was sent by Atlassian JIRA
(v6.2#6252)