Mailing-List: contact fop-user-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: fop-user@xml.apache.org
Message-ID: <40E91642.9040606@hotmail.com>
Date: Mon, 05 Jul 2004 09:50:10 +0100
From: Chris Bowditch <bowditch_chris@hotmail.com>
Reply-To: bowditch_chris@hotmail.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5) Gecko/20031013 Thunderbird/0.3
MIME-Version: 1.0
To: fop-user@xml.apache.org
Subject: Re: Detecting errors in rendering
References: <000301c4626b$209b2e00$3200a8c0@TRITON>
In-Reply-To: <000301c4626b$209b2e00$3200a8c0@TRITON>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

Richard Evans wrote:
> I�ve tried implementing my own Logger and using Driver.setLogger and 
> this does catch some errors.  However other errors (bad property 
> formats, etc) seem to be reported via the static �screen logger�.  I 
> don�t see how I can use the screen logger safely in a multi-threaded 
> environment.

The screen logger is set by:

MessageHandler.setScreenLogger(logger);

However, as you've noticed, in a MT environment, the messages for different 
threads will be mingled together. The way I solved this problem, was to create 
a logger that can have many listeners which each register with the logger. The 
constructor for each listener records the thread name, and when starting a new 
thread, a new listener is registered with the logger. The logger then passes 
its events to registered listeners whose thread name matches the current thread.

I hope this makes sense.

Chris


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org