[jboss-dev] Log4J RepositorySelector

[Dimitris Andreadis]

Can we first discuss the implications that Scott described for jboss
components using commons logging:
(from http://jira.jboss.com/jira/browse/JBAS-1853
<http://jira.jboss.com/jira/browse/JBAS-1853> )
 
"The next level of isolation is to actually create a unique
LoggerRepository for use by the jboss Logger in the Log4jService. The
concern is that components like jgroups, hibernate, tomcat, etc. using
commons logging will fail to pickup the Log4jService LoggerRepository.
We probably need to configure commons logging as well from the
Log4jService with a flag that can disable this."


________________________________

	From: jboss-development-bounces at lists.jboss.org
[mailto:jboss-development-bounces at lists.jboss.org] On Behalf Of Stan
Silvert
	Sent: Thursday, January 25, 2007 8:30 PM
	To: JBoss.org development list
	Subject: [jboss-dev] Log4J RepositorySelector
	
	

	A long time ago when I was still in support I wrote a
RepositorySelector implementation.  This allows a deployment to have its
own logging environment.  But, it was never integrated into JBoss
itself.  Since then, I've been meaning to come back to it and put it
into JBoss: http://jira.jboss.com/jira/browse/JBAS-1313

	 

	As you can see, someone in the community stepped up and built an
implementation.  I took a quick look at it and it looks pretty good.
Seems to work just like it should.

	 

	The question I have is if this is something we want to put into
4.2 at this late hour.  It's a nice feature that we get requests for
from time to time.  What do you guys think?

	 

	Also, since the implementation is based on the old microkernel,
would we want to ask this guy to create a version for JBoss 5 as well?
If so, he may need someone who is available to answer questions.  Right
now I know squat about the new kernel.

	 

	Stan Silvert

	JBoss, a division of RedHat

	ssilvert at jboss.com

	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-development/attachments/20070125/f3c03209/attachment.html