Thread: Logging in the driver

I am looking at trying to debug the driver for staroffice.

Unless someone can tell me otherwise, this requires logging. Currently
the driver has a rudimentary mechanism for logging

DriverManager.println()

This is ok, but it doesn't provide for various levels of debugging.

One possibility is to use something like log4j, but given the recent
distaste for adding binaries to the download I am reluctant to add a
library.

At this point I will probably add for my own purposes a simple logging
system that can be controlled by level.

A while ago someone posted a message which suggested that they had added
instrumentation to the driver. If this person is still on the list,
please contact me.

Cheers,

Dave

* "Dave Cramer" <Dave@micro-automation.net> wrote:
|
| This is ok, but it doesn't provide for various levels of debugging.
|
| One possibility is to use something like log4j, but given the recent
| distaste for adding binaries to the download I am reluctant to add a
| library.

log4j support would have been cool, has we then would have much better
mechanism for controlling logging.

Have you had a look at log4j micro edition ? The API is drop in replacement
for the real thing and the jar file only 25,281 bytes. The size shouldn't
scare anybody, but it would be a required runtime component and that warrants
some discussion...

Check :

http://qos.ch/


--
Gunnar Rønning - gunnar@polygnosis.com
Senior Consultant, Polygnosis AS, http://www.polygnosis.com/