logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "wleana" <wle...@yahoo.com>
Subject Re: static/inherit problem
Date Thu, 03 Apr 2003 22:03:30 GMT
It doesn't make the difference...:-(
Of course, make it non-static will work technically, but conceptually 
it is not correct, and performance-wise not right either...
This should be a very common problem, how does everyone handling this?


--- In Log4J@yahoogroups.com, "Keith Hatton" <khatton@a...> wrote:
> Perhaps something like this:
> 
> class A {
> private static MyLog mLog;
> protected myId;
> A(){
>   this("A");
> }
> 
> protected A(String id) {
>   myId = id;
>   init myLog with myId...
> }
> 
> public void doSth(String aMsg){
>    mLog.debug(aMsg);
> }
> } 
> 
> class B extends A{
> B(){
>   super("B");
>  }
> }
> 
> 
> Keith
> 
> 
> -----Original Message-----
> From: wleana [mailto:wleana@y...]
> Sent: 03 April 2003 10:05
> To: log4j-user@j...
> Subject: static/inherit problem
> 
> 
> Hi, I have a design issue related to the fact that the Logger needs 
> to be static. And suppose I have A and its subclass B.
>  
> I have a wrapper MyLog that wraps around Logger and a myId field of 
> each class, in which, the log message always print out myId of its 
> caller.
> 
> class A {
> private static MyLog mLog;
> protected myId;
> A(){
>   myId = "A";
>   init myLog with myId...
> }
> 
> public void doSth(String aMsg){
>    mLog.debug(aMsg);
> }
> } 
> 
> class B extends A{
> B(){
>  myId = "B";
>  super()
>  }
> }
> 
> When I do this:
> B b=new B();
> b.doSth("blah");
> 
> The log will actually show the caller's myId is "A", instead of "B".
> (you see I even make the myId field non-static because of the same 
> issue, but actually I would like it to be static conceptually)
> 
> I have tried different ways, it only works if mLog is not static, 
the 
> within doSth from class A, it will actually dynamically use object 
of 
> type B's mLog...But we want the Logger class (or its wrapper class) 
> to belong to class not to an object...how should we solve this? 
What 
> should be the right design of this? Please share your thoughts. 
> 
> Thanks a lot.
> -wleana
> 
> 
> --------------------------------------------------------------------
-
> To unsubscribe, e-mail: log4j-user-unsubscribe@j...
> For additional commands, e-mail: log4j-user-help@j...
> 
> 
> --------------------------------------------------------------------
-
> To unsubscribe, e-mail: log4j-user-unsubscribe@j...

> For additional commands, e-mail: log4j-user-help@j...


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org


Mime
View raw message