Hi Paul,
I think moving to slf4j would be great. One of the big issue with the
JDK Logging is that it doesn't allow per webapp configuration, it a
JVM wide configuration which means that configuring for one webapp
could affect the logging of other applications running in the same
JVM.
This is a major drawback when you build an webapp and don't
necessarily control the environment in which it will get deployed (our
customers can chose how they deploy it). All we want/need is to enable
our customers to configure the logging of our application without
affecting other application or even the app server. For this reason I
would strongly suggest moving away from JDK logging.
slf4j is definitely the best choice for logging nowadays and those who
want to ultimately use JDK logging still can with a minimal impact on
performance, permgen etc.
What do you think?
SaM
On Tue, Dec 8, 2009 at 9:09 PM, Paul Sandoz <Paul.Sandoz_at_sun.com> wrote:
>
> On Dec 8, 2009, at 9:28 AM, Robert Naczinski wrote:
>
>> Hi,
>>
>> knows anybody, how I configure logging in Jersey?
>>
>
> Jersey currently uses JDK logging, so any configuration needs to utilize
> that. The current reason for not switching is to avoid adding further
> dependencies. If there are significant advantages we could switch e.g. to
> slf4j.
>
> BTW we need to review the exception throwing and logging in Jersey.
> Currently it's a bit chaotic. For example, we should expose a well-defined
> set of loggers that are publicly available for configuration.
>
> Paul.
>
>
>> We use native Log4J in our projects.
>>
>> Thanx,
>>
>> Robert
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
>> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>