× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Walden H. Leverich wrote:

"Now, what's "conventional wisdom" should I log directly to Log4J, or
should I log via commons-logging?"

The answer of course, is it depends.

The Jakarta-Apache commons logging is supposed to be a light weight 
wrapper that will let you plug in a variety of logging back ends, such as 
Log4J, the Sun JDK logging system, or a specialized J2EE system like WAS. 
The commons logging library will keep the interface simple. So what you 
should be able to do is add a custom Appender class that knows about 
iSeries Job logs and then use it with the commons-logging on an iSeries 
when needed. When your in another environment with another logging system, 
your code shouldn't have to change.

If you know you'll always use Log4J then just stick with that and just 
change you Log4J config file on different platforms.

_________________________________________________________________
Jeff Furgal / MIMIX Product Architect / Lakeview Technology

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.