JDK-4933674 : java.util.logging.LogManager.addPropertyChangeListener needs clarification
  • Type: Bug
  • Component: docs
  • Sub-Component: guides
  • Affected Version: 5.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_2.6
  • CPU: sparc
  • Submitted: 2003-10-07
  • Updated: 2017-05-16
  • Resolved: 2003-12-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 b32Fixed
Description

Name: sdR10048			Date: 10/07/2003


Filed By      : SPB JCK team (###@###.###)
JDK           : java full version "1.5.0-beta-b22"
JCK           : 1.5

Specification excerpt:
======================
--------- J2SE API spec v.1.5 ---------
...
public void addPropertyChangeListener(PropertyChangeListener l)
                               throws SecurityException
Add an event listener to be invoked when the logging properties are re-read. 

Parameters:
l - event listener 
Throws: 
SecurityException - if a security manager exists and if the caller does not have LoggingPermission("control"). 
NullPointerException - if the PropertyChangeListener is null.

...
---------- end-of-excerpt ---------------

Problem description
===================
The designated method's javadoc says nothing about the expected 
behaviour if we add the same listener twice.

======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic tiger-beta FIXED IN: tiger-beta INTEGRATED IN: tiger-b32 tiger-beta VERIFIED IN: tiger-b40
14-06-2004

PUBLIC COMMENTS Putback in build 32 ###@###.### 2003-12-14
14-12-2003

EVALUATION The designated method's javadoc says nothing about the expected behaviour if we add the same listener twice. ###@###.### 2003-10-09 I checked with engineering on this. The issue is: if the same logger is added twice, and one is removed, will it remove both instances? Will fix with the following doc comment: "Adding multiple instances of the same event Listener results in multiple entries in the property event listener table". ###@###.### 2003-11-24
24-11-2003