Martin Burchard wrote:
> Using this way, is it possible to have the Logger configuration also
> on a per Thread basis?
No, SiftingAppender only controls the appenders nested within it. It
does not control the configuration of loggers.
Reading through Chapter 9: Context Selectors I have seen
Thank you, I'll try to understand and implement that.
Using this way, is it possible to have the Logger configuration also on a
per Thread basis?
I know this is also a little bit strange but, we have a lot of different
processes running.
Some do logging using the ALogAppender, some do logging us
Looking at the getNLog() method reproduced below, it seems like
discriminating appenders based on process name would be sufficient.
private boolean getNLog() {
if (nLog == null) {
try {
IProcess process = ProcessManager.getProcess();
logDB = process.getDB("", dbPath,
To give you an impression of the pain of a Domino developer, here is a basic
agent.
package de.pentos.test.agents;
import lotus.domino.AgentBase;
import lotus.domino.AgentContext;
import lotus.domino.Base;
import lotus.domino.Database;
import lotus.domino.Document;
import lotus.domino.NotesExcep
This one...
But the assumption is that I use a Context Selector so only Log events reach
my appender instance that belong to this appender instance.
package de.pentos.domino.logging;
import java.util.ArrayList;
import java.util.Iterator;
import java.util.List;
import lotus.domino.Database;
imp
By the way, what type of appender are you using? Is it a custom made appender
for Domino?
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
___
Logback-user mailing list
Logback-user@qos
See http://logback.qos.ch/manual/appenders.html#SiftingAppender
which will work for all loggers, even those declared statically.
You could either put values in MDC when your thread starts or develop your own
"discriminator" class based on thread ids. A discriminator has to implement
the ch.qo
t; Sent: Thursday, 5 March, 2009 14:26:41 GMT +00:00 GMT Britain, Ireland,
> Portugal
> Subject: [logback-user] ContextSelector and getLogger
>
>
> Hello,
>
> I currently try to get SLF4J and Logback to work on IBM Lotus Domino
> Server
> 8.5.
> It's working.
>
Gulcu
To:
logback users list
Date:
05.03.2009 15:32
Subject:
Re: [logback-user] ContextSelector and getLogger
Sent by:
logback-user-boun...@qos.ch
Hello Martin,
Could you please describe your use case in your terms without assuming the
use
of a ContextSelector?
Martin Burchard wrote:
> Hello,
gging statements would be handled as well.
- Original Message -
From: "Martin Burchard"
To: logback-user@qos.ch
Sent: Thursday, 5 March, 2009 14:26:41 GMT +00:00 GMT Britain, Ireland, Portugal
Subject: [logback-user] ContextSelector and getLogger
Hello,
I currently try to get SL
Hello Martin,
Could you please describe your use case in your terms without assuming the use
of a ContextSelector?
Martin Burchard wrote:
Hello,
I currently try to get SLF4J and Logback to work on IBM Lotus Domino Server
8.5.
It's working.
We need to do logging an a per Thread basis because
Hello,
I currently try to get SLF4J and Logback to work on IBM Lotus Domino Server
8.5.
It's working.
We need to do logging an a per Thread basis because we log into a Domino
database. The Java object of a Domino database is based on a session object,
and that can not exist over more then one thr
12 matches
Mail list logo
