Hi,
Sorry for being late to this discussion. I don't read those lists
continuously any more.
Frank Schönheit schrieb:
Hi,
looking for a possibility to implement some client-side logging
facilities in our database drivers, I came across css.util.logging [1] -
a UNO API which promises to provide exactly such capabilities.
Unfortunately, there's no implementation for this API.
This is not entirely true.
The configmgr backend service has logging capabilities built around this
API. In configmgr/workben/logger a logger component can be built that
takes this log output and dumps it into a file (or on stderr).
If there is trouble with configuration parsing at a customer/user site,
this component can be installed (using the UNO package manager) and
voila - you get log output. The component is crude in some respect (it
is configured via environment variables and the log threshold level is
configured numerically), but it wouldn't take all that much to make it
into something usable.
Furthermore,
trying to implement it revealed some shortcomings, which cannot be
solved with the existing API, since it is already marked "published",
and thus cannot be changed anymore.
I'm not sure which shortcomings you mean and I haven't looked at your
new proposal.
One shortcoming I recall from implementing the above (btw, at that time
I tried to get feedback on a more general logging strategy, but did not
get much of value) is how to obtain a logger for a certain component or
module. As I had nothing to generalize by, I took the simplest solution
for the one-module case I had at hand: the configuration defines a
singleton name, which it will use to get a logger. It doesn't care how
that singleton is populated.
The simple test logger I defined (I also have a multi-platform binary
package for interested parties) registers itself as that singleton. Of
course much more sophisticated solutions that merge and filter log
output from multiple components can also be used in that place.
- Jörg
I'd like to propose a new logging API, which is modeled after the Java
logging API (though not (yet) as powerful).
Since this involves quite a few new types, I will not introduce them
here in this mail, but I uploaded a zipped version of the
autodoc-generated IDL reference for the proposed com.sun.star.logging
module. You can find it at [2].
Feedback to this proposed API is highly welcome.
Thanks & Ciao
Frank
[1]http://api.openoffice.org/docs/common/ref/com/sun/star/util/logging/module-ix.html
[2]http://udk.openoffice.org/servlets/ProjectDocumentList
--
Joerg Barfurth phone: +49 40 23646662 / x66662
Software Engineer mailto:[EMAIL PROTECTED]
Desktop Technology http://reserv.ireland/twiki/bin/view/Argus/
Thin Client Software http://www.sun.com/software/sunray/
Sun Microsystems GmbH http://www.sun.com/software/javadesktopsystem/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
