[ http://issues.apache.org/jira/browse/MYFACES-949?page=comments#action_12415820 ]
Mario Ivankovits commented on MYFACES-949: ------------------------------------------ Simon, we still have a pain reagrding logging, no? If I recap correctly, its still not possible to reload a servlet context without leaking memory. We have to remove "static" from our "log" declaration and make the log creation itself lazy. So instead of creating the log in the constructor like in Log.java associatied to this jira, we need a method getLog() which will do the job, now that we no are no longer "static" there is no need to make it thread-safe. Is this all true? If so, we could raise this one additonal time on myfaces-dev - and - hey - simon, you are free to move on then ;-) > New logging framework for MyFaces code > -------------------------------------- > > Key: MYFACES-949 > URL: http://issues.apache.org/jira/browse/MYFACES-949 > Project: MyFaces Core > Type: Improvement > Components: General > Reporter: Simon Kitching > Assignee: Simon Kitching > Attachments: Log.java, LogFactory.java > > Logging for MyFaces classes has been discussed here: > http://mail-archives.apache.org/mod_mbox/myfaces-dev/200512.mbox/[EMAIL > PROTECTED] > and especially here: > http://mail-archives.apache.org/mod_mbox/myfaces-dev/200512.mbox/[EMAIL > PROTECTED] > Attached are classes intended to go in the "share" code which provide a > logging API in the package "org.apache.myfaces.logging". > This means all MyFaces code that wants to log can do so without any explicit > dependency on an external logging library. > The implementation simply forwards directly to commons-logging in a pretty > efficient way. > These logging classes do *not* provide the ability to swap the underlying > logging library at runtime like commons-logging does; it simply centralises > the logging lib dependency into one class (org.apache.myfaces.logging.Log) > instead of spreading it out across all MyFaces classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
