I've already tried that approach, but the problem is that there seems to be a single JackRabbit logger named 'logger$', or am I wrong?

Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (R&D)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes
(56-2) 335 2461
gvasquez@altiuz.cl
http://www.altiuz.cl
 


El 30-05-2012, a las 15:40, ceki escribió:


Sounds like setting the root level to INFO or higher and setting the level of the appropriate JackRabbit loggers to DEBUG would work. Right?

On 30.05.2012 21:30, Gonzalo Vasquez wrote:
Yes I have. All I need to log is in the DEBUG level of JackRabbit, but I
only need messages from specific classes, that's my problem :(

Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (R&D)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes
(56-2) 335 2461
gvasquez@altiuz.cl
http://www.altiuz.cl



El 30-05-2012, a las 13:25, ceki escribió:


Hi Gonzalo,

Have you looked at the basic selection rule [1]?

HTH,

[1] http://logback.qos.ch/manual/architecture.html#basic_selection

--
Ceki
http://twitter.com/#!/ceki

On 30.05.2012 17:29, Gonzalo Vasquez wrote:
I can't seem to find out how to filter my logs bases on the class name
that issued the logged statement. Is any of of the pre-shipped filters
suitable for this task?

Regards,



--
Ceki
http://twitter.com/#!/ceki
_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-user