[
https://issues.apache.org/jira/browse/JSPWIKI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631907#action_12631907
]
Harry Metske commented on JSPWIKI-376:
--------------------------------------
I'm trying to imagine how this all works on the "problem" AppServers like
WebSphere and JBoss.
If we keep shipping log4j.jar in WEB-INF/lib like we do now, I doubt that the
classloading issues will be gone.
If that is the case, then deploying JSPWiki on WebSphere or JBoss still
requires some shuffling of jar files around (which is no different than now).
Since solving the classloading issue was the primary reason for introducing
slf4j, we should first know for sure if this can be solved and how.
I can do some investigation on this (unless somebody already know the answers
off course)
> Move from log4j to slf4j
> ------------------------
>
> Key: JSPWIKI-376
> URL: https://issues.apache.org/jira/browse/JSPWIKI-376
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Reporter: Janne Jalkanen
> Fix For: 3.0
>
>
> SLF4J allows far more flexible logging than log4j, and it would allow us to
> get rid of these dumb log4j compatibility problems that sometimes occur. It
> also plays better with other applications, gives the user more power to
> choose how to log his stuff, and is also pretty cool otherwise. The change
> would be relatively trivial, and would probably be largely invisible to the
> users (since we could continue shipping with necessary log4j jars).
> http://www.slf4j.org
> The license is MIT/X11, so that's fine.
> Opinions?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
