You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2002/07/23 13:31:04 UTC
DO NOT REPLY [Bug 11078] New: -
Subclassing
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11078>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11078
Subclassing
Summary: Subclassing
Product: Log4j
Version: 1.2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Configurator
AssignedTo: log4j-dev@jakarta.apache.org
ReportedBy: t.schoellhorn@wissenswerk.com
I think I discovered a bug, when I want to use a subclass of the class Logger.
I use the DomConfigurator to configure Log4j and want to use a subclass of
Logger.
It works fine when I specify the class in each category like
<code>
<category name="net.NetTools" class="wwerk.wnetz.system.Logger"
additivity="false">
<priority value="DEBUG"/>
<appender-ref ref = "GUI"/>
</category>
<categoryFactory class="wwerk.wnetz.system.TheLoggerFactory"/>
</code>
If I dont specify the class in each category I get a ClassCastException when I
want to get a named Logger-Instance.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>