I'm currently trying to release the next version of my package
org.netrexx.runtime.compatibility
on www.kenai.com, Project netrexx.
There is one still pending issue there:
Remove the *cyclic* dependency between class RexxFile and class RexxMsg,
which the current
version still does have, as I did implement originally my own logging
mechanisms, using
basically RexxFile.lineout() as documented in the Rexx2Nrx RunTime Docu..
I did now, *after searching via Google *Java Log* find the quite useful
link:
http://openbook.galileocomputing.de/java7/1507_20_001.htmlwhich, in particular, discusses the two nowadays available major options:
java.util.logging (JUL)
*and*
Logging with Log4j (
http://logging.apache.org/log4j/1.2As I did support logging in class RexxMsg since the first release of
Rexx2Nrx, and it's run-time library,
and shall want and need to remain upwards compatible for the supoorted
methods
info, warning, error, abort etc, I still have to come-up with a decision
now whether to
use
java.util.logging (JUL)
*or*
log4j
I still have to finish reading about log4j, but do want to ask now the
more experienced
Java experts here which way we shall & should prefer for NetRexx
applications!
Thus, I'm asking here for your recommendations, and, preferable,
*decision* on this topic.
Kind regards from Vienna,
Thomas Schneider
PS: Happy Birthday, of course to Rexx, and thanks to MFC for inventing
all this :-)
.
--
Thomas Schneider, IT Consulting;
http://www.thsitc.com; Vienna, Austria,
Europe
_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive :
http://ibm-netrexx.215625.n3.nabble.com/
Thomas Schneider, Vienna, Austria (Europe) :-)
www.thsitc.com
www.db-123.com