Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: 202.81.18.155 is neither permitted nor
 denied by domain of paulex.yang@gmail.com)
Message-ID: <44FD437E.8050600@gmail.com>
Date: Tue, 05 Sep 2006 17:29:34 +0800
From: Paulex Yang <paulex.yang@gmail.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib][logging] a test suite shouldn't touch any of JRE
 config
 files!!!
References: <6e47b64f0608292203w34129210ra72dd4c66463e53c@mail.gmail.com>
	 <4d0b24970608300004h2dac39mda65662e43a7635a@mail.gmail.com>
	 <6e47b64f0608300020j109b3181pade98a12130be4e4@mail.gmail.com>
	 <4d0b24970608300137v5901a5f5xf9d66a85c96faea6@mail.gmail.com>
	 <6e47b64f0608310140v1d82aabjc09778b9e276551f@mail.gmail.com>
	 <44F7D595.7070900@gmail.com>
	 <6e47b64f0609040247y6eaf74a2he806e511e76b4d58@mail.gmail.com>
	 <44FBF96E.8080801@gmail.com>
	 <6e47b64f0609042255n4cf73c7bra0bc9e1d84fcf6c@mail.gmail.com>
	 <44FD175C.20904@gmail.com>
 <6e47b64f0609050200p8477a46x146a73ceac3fa806@mail.gmail.com>
In-Reply-To: <6e47b64f0609050200p8477a46x146a73ceac3fa806@mail.gmail.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Stepan Mishura wrote:
> Paulex, thanks for your patience and answers.
>
> Yes, Sun's JRE sets root logger's level according to
> 'lib/logging.properties'. Also specifying the level for root logger in
> j.u.l.config.file doesn't help. (I assumed before that a JRE respects my
> "lovely" custom LogManager settings :-(! )
>
> OK. Let's return to the initial issue: how to run logging tests without
> changing JRE config files?
>
> I still believe that there should be some elegant way for testing logging
> implementation without touching JRE files. 
I agreed this is not acceptable. AFAIK current LogManagerTest has used a 
MockLogManager in most test cases, so the migration should be relatively 
easy.
> For example, what
> about developing custom LogManager for testing? The testing manager will
> work in 2 modes: default configuration and custom configuration. A 
> test will
> have a hook to switch testing manager's mode. The first configuration is
> read from JRE config files (by j.u.l.LogManager implementation) and the
> second one will be fully controlled by a test and is set by the test
> via some manager's method (say readConfiguration(InputStream)). Does this
> sound crazy?
Maybe we just need one Support_Exec() invocation to verify if the 
LogManager reads the default logging 
properties(jre/lib/logging.properties) correctly(which should be 
straightforward by also loading and parsing that properties in test 
codes), for other tests, we always use customized LogManager or 
configuration files. If you are fine with this, I'm volunteer to 
refactor the tests.
>
> Thoughts? Other suggestions?
>
> Thanks,
> Stepan Mishura
> Intel Middleware Products Division
>
> ------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>


-- 
Paulex Yang
China Software Development Lab
IBM


---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org