camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CAMEL-6133) Logger destroyes SaxSource
Date Wed, 06 Mar 2013 09:38:13 GMT
Thomas  created CAMEL-6133:
------------------------------

             Summary: Logger destroyes SaxSource
                 Key: CAMEL-6133
                 URL: https://issues.apache.org/jira/browse/CAMEL-6133
             Project: Camel
          Issue Type: Bug
          Components: camel-core
    Affects Versions: 2.10.4
            Reporter: Thomas 


Test case:
To parse XHTML we use jtidy and a xslt script. The xslt component works in this case better
when a SAXSource is used because the SAXSource can use it's own XMLReader with it's own CatalogResolver.


Problem:
After transforming the body with xslt component the SAXSource is debug logged by _org.apache.camel.processor.SendProcessor_.
This log will "destroy" the SAXSource resulting in an _premature end of file_. See http://www.danielschneller.com/2008/01/saxparseexception-1-1-premature-end-of.html

Workaround:
Switch log level of _SendProcessor_ to INFO or WARN or something else but not DEBUG.

Logging in camel should clone SAXSource before reading.

May be a problem by used logger framework? I use log4j.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message