[Tm4j-developers] Thoughts on logging

[Kal A. <ka...@te...>]

Hi all,

I'm in the process of working out how we can rationalise the logging in T=
M4J.=20
First of all I propose that for 0.7.0 we continue to use Log4J - despite=20
JDK1.4 now having its own logging mechanism.

Secondly I would like to make sure that all logging is generated using th=
e=20
org.tm4j prefix for the logging category.

Thirdly, I would like to move away from the use of class names for logs t=
o=20
using specific log names for specific *areas* of functionality. This may =
mean=20
that certain classes will end up writing to multiple logs (though I doubt=
=20
that this will be very common in our code base).

Here is my proposal for the initial set of logging categories. Please hav=
e a=20
look over this and let me know if there are any cateories missing or uncl=
ear.

org.tm4j.topicmap=09- Log all messages to do with basic topic=20
=09=09=09  map processing. Also use to log less verbose
=09=09=09  messages from the backend (e.g "Cannot open
=09=09=09  database")

org.tm4j.topicmap.index  - Indexing related messages

org.tm4j.topicmap.parser - Topic map parsing and building messages

org.tm4j.topicmap.backend.ozone - Ozone specific messages

org.tm4j.topicmap.backend.dom   - DOM backend messages

org.tm4j.topicmap.events - Logging of event processing / handling

org.tm4j.topicmap.tolog  - Logging of query processing

org.tm4j.net - Logging of locator parsing/resolution messages

Cheers,

Kal

--=20
Kal Ahmed, tecqhuila.com
XML and Topic Map Consultancy

e: ka...@te...
p: +44 7968 529531
w: www.techquila.com