RFR 8150840: Add an internal system property to control the default level of System.Logger when java.logging is not present.

Roger Riggs Roger.Riggs at Oracle.com
Fri Mar 4 17:05:51 UTC 2016


I thought about that also but it is one of those cases where where it is 
'too early' for method refs.

Roger


On 3/4/2016 11:56 AM, David Lloyd wrote:
> Can they be method refs, or is this one of those cases where it could
> be early boot where none of that stuff works yet?
> --
> - DML
>
>
>> On Mar 4, 2016, at 10:19 AM, Roger Riggs <Roger.Riggs at Oracle.com> wrote:
>>
>> Hi Daniel,
>>
>> Good idea.
>>
>> SimpleConsolerLogger.java:
>>    Some of the property accesses could use the existing property actions instead of anonymous inner classes.
>>
>> static Level getDefaultLevel() {
>> String levelName = AccessController.doPrivileged( new sun.security.action.GetPropertyAction("jdk.system.logger.level", "INFO")); ...
>>
>> Roger
>>
>>
>>
>>> On 3/4/2016 6:48 AM, Daniel Fuchs wrote:
>>> [Resending with a link to the patch]
>>>
>>> Hi,
>>>
>>> Please find below a patch for:
>>>
>>> https://bugs.openjdk.java.net/browse/JDK-8150840
>>> 8150840: Add an internal system property to control the default
>>>          level of System.Logger when java.logging is not present.
>>>
>>> http://cr.openjdk.java.net/~dfuchs/webrev_8150840/webrev.00
>>>
>>> This patch also introduces a better separation between the
>>> SimpleConsoleLogger (created by the DefaultLoggerFinder
>>> when java.logging is not there), and the SurrogateLogger,
>>> which emulates the behavior of java.util.logging.Logger
>>> when java.logging is present but there is no custom
>>> configuration (used to be PlatformLogger.DefaultLoggerProxy).
>>>
>>> best regards,
>>>
>>> -- daniel




More information about the core-libs-dev mailing list