Yes, this is very unfortunate indeed. It's even more annoying taking
into account that this issue has been fixed in tomcat
(
http://tomcat.apache.org/tomcat-5.5-doc/logging.html see
java.util.logging) and I always thought that tomcat is encapsulated in
glassfish one way or another. Right now the outcome is that
java.util.logging package is completely unusable. For all glassfish
developers reading this list: please fix that ASAP.
Cheers,
Jakub
On Fri, Sep 26, 2008 at 6:36 PM, <glassfish_at_javadesktop.org> wrote:
> No, not really. The logging in Glassfish is global to the entire app server.
>
> Log4j has the advantage that it's loggers can be loaded in to the individual classloaders the different web apps, whereas java.util.logging, which comes from the system class path isn't so fortunate.
>
> Also, by being global, there is a potential security risk since any application deployed in the server can potentially access and intercept the logs of any other application on the server.
>
> Not so much an issue with 99.999% of the deployments out there, but if you're running your application on a shared GF server out in the wild, then I'd be more careful what I logged.
>
> I don't know if GFv3 is going to be able to address this issue or not.
>
> I filed an issue on this a long time ago: https://glassfish.dev.java.net/issues/show_bug.cgi?id=3100
> [Message sent by forum member 'whartung' (whartung)]
>
> http://forums.java.net/jive/thread.jspa?messageID=301851
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>