[
https://issues.apache.org/jira/browse/SLING-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-674.
-----------------------------------
Resolution: Fixed
Fixed in Rev. 698974.
> Replace tomcat juli by our own implementation
> ---------------------------------------------
>
> Key: SLING-674
> URL: https://issues.apache.org/jira/browse/SLING-674
> Project: Sling
> Issue Type: Improvement
> Components: Scripting JSP
> Affects Versions: Scripting JSP 2.0.2
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Scripting JSP 2.0.4
>
>
> The Jasper compiler and EL implementations use a Tomcat specific logger
> called "juli". This logger is a copy of the commons-logging API but in a
> different package (org.apache.juli.logging). The default implementation of
> the Tomcat juli library uses the JDK logger for logging. This is not what we
> want in Sling, because we are basing alls logging on SLF4J.
> To fix this situation, the scripting/jsp bundle should have its own
> o.a.juli.logging package, which also defines the LogFactory class and Log
> interface for use by Jasper but which is backed by SLF4J loggers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
