Two logging questions

[Mogens Nidding]

Hi! Does anyone have a suggestion for "delivering" the logging aspect of the SCJD?

I am getting to the point where I want to finish up the assignment and send it out the door. I did some logging on the server side to help myself. In addition, whenever my GUI catches an exception, it logs the stack trace and displays an error dialog along the lines of "could not book this and that contractor, log file may include details".

Do you think this approach of referring to a logged exception from an error dialog is acceptable? It has the advantage of sheltering non-technical users from having to look at the arbitrarily complex jibberish that might be in an exception message.

The other concern I have is that there is a requirement saying that everything that is configurable must be so from the GUI and persist its settings in suncertify.properties - and at this point, I don't want to make it more configurable than absolutely needed, since it's just adding "more of the same" to my config GUI/model. What is the minimum thing I can do that is still decent?

Among the things I am considering is hardcoding the logging configuration to outputting INFO to the console.
[ October 09, 2004: Message edited by: Nicky Bodentien ]

[Anton Golovin]

 

Originally posted by Nicky Bodentien:
Hi! Does anyone have a suggestion for "delivering" the logging aspect of the SCJD?

I am getting to the point where I want to finish up the assignment and send it out the door. I did some logging on the server side to help myself. In addition, whenever my GUI catches an exception, it logs the stack trace and displays an error dialog along the lines of "could not book this and that contractor, log file may include details".

Do you think this approach of referring to a logged exception from an error dialog is acceptable? It has the advantage of sheltering non-technical users from having to look at the arbitrarily complex jibberish that might be in an exception message.

The other concern I have is that there is a requirement saying that everything that is configurable must be so from the GUI and persist its settings in suncertify.properties - and at this point, I don't want to make it more configurable than absolutely needed, since it's just adding "more of the same" to my config GUI/model. What is the minimum thing I can do that is still decent?

Among the things I am considering is hardcoding the logging configuration to outputting INFO to the console.

[ October 09, 2004: Message edited by: Nicky Bodentien ]

Hi, Nicky!

My project provides three lines in the suncertify.properties file:

canonical path to the local db file
url to the remote data source (all, including the remote object name)
canonical path to the server db file

[Mogens Nidding]

Thanks, Anton!

So did you hardcode your logging configuration? Or did you just not use logging?