it seems very odd to me that an embedded database would feel free to reset the logging configuration of the entire application. as it is, our application does programmatic configuration of the java.util.logging framework upon startup. however, when we attempt to open an hsqldb database, the FrameworkLogger class resets the jdk LogManager to its original configuration.
i'm surprised that this is not the default behavior, but at the very least there should be a configuration setting for telling hsqldb to leave the logmanager alone.
James Ahlborn ( jahlborn ) - 2011-02-28 12:29:56 PST
|status_id||Open||2011-03-14 03:50:25 PDT||fredt|
|priority||5||2011-03-14 03:50:25 PDT||fredt|
|close_date||-||2011-03-14 03:50:25 PDT||fredt|
|resolution_id||Accepted||2011-03-07 09:06:40 PST||unsaved|
|resolution_id||None||2011-03-03 14:07:22 PST||unsaved|
|assigned_to||nobody||2011-03-01 12:29:59 PST||fredt|