Hi:
The jPOS logger is a different thing altogether. Please get to know it
through docs, the source code, examples. It's not meant to replace your
traditional logger, although it could if you wanted! In summary, it has a
different set of objectives and features that are unique for OUR type
of applications. Our log is meant to be parseable... For example,
yesterday I had to create a report of transactions which were missing
some elements within an ISOMsg opaque field which we don't log in the
database. Easy, we ran a program to parse the xml, extract the
information and create a report.... Can you do that w/ log4j?
The jPOS logger architecture lets us modify log messages in flight. For
example, we could make it so the logger masks or wipes sensitive data
before logging an event. Can you automatically do that w/ log4j?
Nonetheless that doesn't mean you can't use another logger alongside. In
fact, in the jPOS-EE project we have a 'jposee-logback' module that
unifies logging from log4j,commons-logging,slf4j into the logback api.
By default in the configuration, the logback messages are routed to the
Q2 logger, but you could configure it so it logs to a traditional set of
files in the 'log' directory and you'd have the best of both worlds...
The reason that I like this approach is that components we use such as
Hibernate, JE, etc, they use a traditional logger so when an error
occurs I'd like to be able to see what happened without having two files
open - I only look at the Q2 log :)
/V
April 17, 2014 at
12:18 AM