[
https://jira.jboss.org/jira/browse/JGRP-1106?page=com.atlassian.jira.plug...
]
Bela Ban resolved JGRP-1106.
----------------------------
Resolution: Done
Yes, this makes sense, thx for the contribution Shay !
I applied this change, but changed the system prop to jgroups.logging.log_factory_class.
Also, I'm not too sure about whether Class.forName() is good. We usually use
Util.loadClass() to make sure to pick the right classloader.
This is in CVS, can you take a look ?
I'll close this issue, feel free to re-open if you run into an issue.
Custom LogFactory instead of the built in log4j / jdk logging
-------------------------------------------------------------
Key: JGRP-1106
URL:
https://jira.jboss.org/jira/browse/JGRP-1106
Project: JGroups
Issue Type: Feature Request
Reporter: Shay Banon
Assignee: Bela Ban
Fix For: 2.8
Attachments: CustomLogFactory.java, LogFactory.java
Hi,
I would love to be able to plug into jboss my own construction of loggers and not rely
on the built in ones. I do some special things when constructing loggers (I am using slf4j
ontop of log4j, but I modify the loggers a bit). Also, I would love to change categories
and such on the fly.
For that, I am attaching two files. The first is an interface called CustomLogFactory
which needs to be implemented to provide the custom implementation. The second is a
modified LogFactory in order to support that. I apologize for not attaching a patch, I
can't seem to connect to CVS, and I am hoping to get this into 2.8 if possible ;), so
I want to provide this as fast as possible.
If this can make it into 2.8 it would be great!
Cheers,
Shay
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira