On 5/31/07, Ken Paulsen <Ken.Paulsen_at_sun.com> wrote:
>
>
> We have to go through a legal review (if it hasn't been done already)
> for 3rd party jars / files. log4j and commons-logging are allowed.
> However, I have been trying to use as few as possible jars in order to
> keep samples simple and small. For logging, I prefer jul which is what
> GlassFish uses and supports very will via it's administration....
> however, this isn't "the law." ;)
>
Personally, I *really* don't like jul. Unless I'm mistaken, to change the
logging prefs I either have to change a file in my JDK/JRE directory, or
write a custom FileHandler. It gets even worse (no offense) when running
under GlassFish, as GF takes steps to capture all jul output and send it to
the server log, so all the work I go through to segregate all my logging
output into application-specific log files is overridden by the container.
Yuck. I prefer putting one extra jar and a config file for log4j in the
root of my app's classpath to configure my logging and get exactly what I
asked for with a minimum of fuss. I know this isn't really the forum for
venting about the vileness of jul, but there it is... :P
--
Jason Lee, SCJP
JSF RI Dev Team
http://blogs.steeplesoft.com