RFR: 7159567 - inconsistent configuration of MemoryHandler (original) (raw)
Jim Gish jim.gish at oracle.com
Wed Sep 26 22:21:30 UTC 2012
- Previous message: hg: jdk8/tl/langtools: 7188968: New instance creation expression using diamond is checked twice
- Next message: RFR: 7159567 - inconsistent configuration of MemoryHandler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sorry -- wrong list -- I mean to send to the openjdk list.
On 09/26/2012 05:19 PM, Jim Gish wrote:
Please review http://cr.openjdk.java.net/~jgish/Bug7159567-set-MemoryHandler-target/ <http://cr.openjdk.java.net/%7Ejgish/Bug7159567-set-MemoryHandler-target/>
Overview - currently you can sub-class java.util.logging.MemoryHandler and specify its configuration in a logging.properties file via the classname. For example, if com.foo.MyMemoryHandler extends MemoryHandler, you can have: logging.properties: com.foo.MyMemoryHandler.push=WARNING com.foo.MyMemoryHandler.level=FINEST .... etc. However, the only way to specify target is by using the global property, java.util.logging.MemoryHandler.target. For example, java.util.logging.MemoryHandler.target=java.util.logging.ConsoleHandler This is clearly broken. This bug fix allows you to say: com.foo.MyMemoryHandler.target=java.util.logging.ConsoleHandler Thanks, Jim
-- Jim Gish | Consulting Member of Technical Staff | +1.781.442.0304 Oracle Java Platform Group | Core Libraries Team 35 Network Drive Burlington, MA 01803 jim.gish at oracle.com
- Previous message: hg: jdk8/tl/langtools: 7188968: New instance creation expression using diamond is checked twice
- Next message: RFR: 7159567 - inconsistent configuration of MemoryHandler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]