Re: Little bug (but very important for me) in LogBrokerMonitor

[Ceki Gülcü]

At 16:25 24.10.2002 +0200, [EMAIL PROTECTED] wrote:

Hello,


[snip]


requestClose() is called by a window closing event and by "close" via menu,
requestExit() ist called by "exit" via menu.
As I am not able to compile the Log4J sources myself, I would be glad if
someone could do that for me and send me the *.jar file, the earlier the 
better

Why can't you compile log4j? The sources are all there!


;-)

Thank you

Regards

Julian Ruhe, DaimlerChrysler Corp. Berlin, Germany
--


--
Ceki

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Little bug (but very important for me) in LogBrokerMonitor

[Julian.Ruhe]

Hello,

I found a bug in LogBrokerMonitor(). I seriously need the 
setCallSystemExitOnClose() method to work properly, in both versions "true" and 
"false".
When I was checking the sources, I found out that the user setting is simply 
overwritten in 
 
protected void requestClose() {
setCallSystemExitOnClose(false);   <-- this overwrites the user setting 

closeAfterConfirm();
 }

and

protected void requestExit() {
_mruFileManager.save();
setCallSystemExitOnClose(true);<--this is OK
closeAfterConfirm();
}


requestClose() is called by a window closing event and by "close" via menu, 
requestExit() ist called by "exit" via menu.
As I am not able to compile the Log4J sources myself, I would be glad if 
someone could do that for me and send me the *.jar file, the earlier the better 
;-)

Thank you

Regards

Julian Ruhe, DaimlerChrysler Corp. Berlin, Germany
--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Little bug (but very important for me) in LogBrokerMonitor

[Ceki Gülcü]

At 17:02 23.10.2002 +0200, [EMAIL PROTECTED] wrote:


As I am not able to compile the Log4J sources myself, I would be glad if
someone could do that for me and send me the *.jar file, the earlier the 
better
;-)

Why can't you compile the log4j sources? What is stopping you?


Thank you

Regards

Julian Ruhe, DaimlerChrysler Corp. Berlin, Germany
--


--
Ceki

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Little bug (but very important for me) in LogBrokerMonitor

[Julian.Ruhe]

Hello,

I found a bug in LogBrokerMonitor(). I seriously need the 
setCallSystemExitOnClose() method to work properly, in both versions "true" and 
"false".
When I was checking the sources, I found out that the user setting is simply 
overwritten in 
 
protected void requestClose() {
setCallSystemExitOnClose(false);   <-- this overwrites the user setting 

closeAfterConfirm();
 }

and

protected void requestExit() {
_mruFileManager.save();
setCallSystemExitOnClose(true);<--this is OK
closeAfterConfirm();
}


requestClose() is called by a window closing event and by "close" via menu, 
requestExit() ist called by "exit" via menu.
As I am not able to compile the Log4J sources myself, I would be glad if 
someone could do that for me and send me the *.jar file, the earlier the better 
;-)

Thank you

Regards

Julian Ruhe, DaimlerChrysler Corp. Berlin, Germany
--
To unsubscribe, e-mail:   
For additional commands, e-mail: