Yes you are right but ...
using a timer would force the usage of 2 different approaches / pieces
of code :
1ø. For normal code
2ø. For EJB / Application Server
Can you elaborate? I don't see why a Timer would be a problem for EJBs. In fact
writing to a file itself is not recommened
Yes you are right but ...
using a timer would force the usage of 2 different approaches / pieces
of code :
1°. For normal code
2°. For EJB / Application Server
Thomas,
Milind Rao wrote:
Any help from some one with more experience with log4j would be appreciated.
One other thing I
Any help from some one with more experience with log4j would be appreciated.
One other thing I noticed with the DailyRollingFileAppender is that no timer is being
used. So when the rollover time
occurs, a new file is not created. A new file is created only on the first log event
after the
I'm looking at using log4j to do logging in our application. Multiple clients on
different machines will be logging events.
The Message object in the LoggingEvent class is an instance of a proprietary Log
class that contains a date. The Log
class implements ObjectRenderer and contains a
