Mailing-List: contact dev-help@excalibur.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Excalibur Developers List" <dev@excalibur.apache.org>
Message-ID: <410E38E5.80509@jicarilla.org>
Date: Mon, 02 Aug 2004 14:51:49 +0200
From: Leo Simons <lsimons@jicarilla.org>
User-Agent: Mozilla Thunderbird 0.6 (Macintosh/20040502)
MIME-Version: 1.0
To: Excalibur Developers List <dev@excalibur.apache.org>
Subject: Re: Question about closing a LogKit PriorityFilteringTarget
References: <4109DA6D.60008@tanukisoftware.com>
In-Reply-To: <4109DA6D.60008@tanukisoftware.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Leif Mortenson wrote:
> I can not think of any reason why you would not want to
> close down the wrapped log targets in the first place.

IMHO in general if you wrap something you should not assume you can kill
it off later. It's not quite as bad as trying to call stop()/dispose()
on something you look up through a service manager, but it can have the
same results :/

Rather, whatever creates the thing that is wrapped should kill that
thing (thou shall cleane up thine owne mess). My guesss is the best
solution is to refactor the relevant container/excalibur-logger code to
keep track of all the real log targets (not just the wrapped stuff) and
do the closing. But I'm blessed with infamiliarity with most of that
code :-D

cheers,

- LSD


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/