Our app will log 3 categories of events: debug, error, and "workflow". The first two obviously fit well with Log4J. The "workflow" category is for application events like "finished step N of job Z". These will be relatively infrequent (at least minutes between) and we would never configure them off. We plan to record debug with a RollingFileAppender and would typically configure it as turned off. We want to send error and workflow via JMS (JMSAppender?) to a MDB that will write them to two separate database tables. I assume we would use a custom "workflow" Level to differentiate the appender.
The workflow messages will have some structure -- at least job name, step name, and date/time. Options I see are: A) Log as text and parse fields in MDB before persisting. B) Log is an object to retain structure and avoid parsing. C) Skip Log4J and write custom code for sending via JMS.
Is Log4J a good choice for our "workflow" messages? Is option B even possible? (Relates to this topic.)
Thanks much! [ March 13, 2007: Message edited by: Bill Compton ]