United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6235077 javax.management.timer.Timer doc inconsistent about what happens for Date in the past
JDK-6235077 : javax.management.timer.Timer doc inconsistent about what happens for Date in the past

Details
Type:
Bug
Submit Date:
2005-03-02
Status:
Closed
Updated Date:
2010-07-29
Project Name:
JDK
Resolved Date:
2006-01-04
Component:
core-svc
OS:
generic
Sub-Component:
javax.management
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
6
Fixed Versions:

Related Reports

Sub Tasks

Description
Prior to version 1.2 of the JMX Specification, the Timer service was defined to throw an exception if a notification was scheduled for a time in the past.  Starting from version 1.2, the more logical behaviour of sending the notification immediately in this case was introduced.  However, some of the documentation for javax.management.timer.Timer still reflects the old behaviour.  In particular, the Notes in the class documentation include one that says (in so far as it can be deciphered) that past-time notifications will be ignored, and the @throws documentation for the IllegalArgumentException says it is thrown for a past date.
###@###.### 2005-03-02 19:09:58 GMT

                                    

Comments
EVALUATION

Clarify the expected behavior for past-time notifications:

If a timer notification is scheduled for a time in the
past a notification should be sent immediately.
###@###.### 2005-04-19 15:05:08 GMT

Spell out in the throws clause of all the Timer.addNotification
methods that IllegalArgumentException is thrown when the supplied
Date is null.
###@###.### 2005-06-07 13:00:32 GMT
                                     
2005-04-19



Hardware and Software, Engineered to Work Together