On Thu, 04 Nov 2004 15:19:06 +0000, Chris Turner <[EMAIL PROTECTED]> wrote:
> my own projects. However a number of my corporate customers dictate that jdk
> logging must be used for all application logging on all projects. They have
> non-Java support staff who are familiar with jdk log output and so on. Thus
Interesting... I remember thinking that there's be this sort of
thing someday when the first suggestions were made about the JDK
including it's own logging rather than using log4j. (I've no idea how
feasible that would have been, it just seems a shame they
couldn't/didn't.)
Anyway, thanks for the comments and with that sort of senario, which
I've been fortunate to have avoided so far, I can only agree that
clogging is the only way to go for Wicket! Hopefully, we won't come
across any issues anyway but do tend to agree with you that gains of
getting it into more places should outweigh the potential downside.
Cheers,
Gwyn
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Wicket-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-user
