>> I would log to the database. In the same transaction as the operation you want to log about. <<
Beware ... this approach will never record any failed transactions, because the logging will be rolled back along with everything else! It really depends on what you really mean by 'reliability'. If you have some statutory or regulatory requirement to audit data you probably need some sort of transaction manager, so that you know the logging has been committed to storage. Log4J 'off-the-shelf' is not this kind of solution, though you might well be able to integrate it somehow (with the right kind of appender). Keith --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
