[logback-user] SecurityManager issue using logback

Andrew Bourgeois andrew.bourgeois at hotmail.com
Sat Nov 5 12:47:25 CET 2011

Hello Ceki

the example you gave me yesterday without logging DIDN'T throw an exception.
This is what I replied yesterday (maybe the sentence is wrong?):
"I wanted to say 'This code runs FINE indeed', so yes, without exceptions."

So to reformulate:
The exception IS thrown when we have SLF4J code
The exception ISN'T thrown when we remove the SLF4J.

Thank you for your time!

Best regards

Andrew Bourgeois

-----Original Message----- 
From: ceki
Sent: Saturday, November 05, 2011 12:09 AM
To: logback users list
Subject: Re: [logback-user] SecurityManager issue using logback

The sample throws an exception when no logging library is present. So
the issue is unrelated to logback, log4j, slf4j or any other logging
library. If the code works with log4j, I am inclined to think that
there other change you are not taking into account.

Again, the sample code throws an exception when no logging library is
present. You should look into that first.


On 05/11/2011 12:00 PM, Andrew Bourgeois wrote:
> Hello
> Ceki said my “bug” report isn’t actually a bug, but didn’t have the tell
> to tell me what’s wrong:
> http://jira.qos.ch/browse/LBCLASSIC-304
> Can anyone here help?**In short:
> package be.removed.fun.removed;

Logback-user mailing list
Logback-user at qos.ch

More information about the Logback-user mailing list