RE: Job Log

["David Morris" <David.Morris@xxxxxxxxxxxxx>]

Aden,

You can have your cake and eat it. Like Joe, I use a logging
framework, in this case LogKit. I have a class that in our package
that contains a static org.apache.log.Logger. I did something
similar for messages. I don't know about JLog, but with LogKit,
you can extend the Logger class you can change the target of
logging. That way if you get a message that is an error, you can
send it to the joblog as well as your logfile. You can even send
an email if appropriate. If it is a debugging message you can do
something different.

I would definitely encapsulate this though. It is going to change
and if you tie yourself into one implementation, you are going to
be stuck. The overall structure of the 1.4 logging support is very
similar to LogKit. Biggest difference I've seen is the support for
assert.

David Morris

>>> Etienne.Richards@penske.com 02/11/02 08:11AM >>>
Joe,

It seems like some of the AS/400 users (where I work) is not that
comfortable with the concept of going and looking in file on the IFS
to
track down possible problems that were logged. I was hoping to get the
best
of both worlds. I am close to abandoning the idea.

When will JDK 1.4 be available on the AS/400?

Etienne

-----Original Message-----
From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
Sent: Monday, February 11, 2002 10:09 AM
To: java400-l@midrange.com
Subject: RE: Job Log


> From: Richards, Etienne
>
> Last week I asked about writing information to the job log from
Java.

Etienne, I'm not sure if there's a business reason why you chose to use
the
job log, but there are some other very good options for logging.
Currently,
I use the IBM JLog package (I got it from IBM's Alphaworks).  It allows
you
to log all different kinds of information, log it to a console, to a
file,
or even to your own logging method, turn it on and off
programmatically, and
so on.  It's been great for me.

Joe