Skip to main content

[jsr236-spec issues] [JIRA] Created: (CONCURRENCY_EE_SPEC-31) Inconsistency in ManagedTaskListener#taskAborted javadoc

  • From: "anthony.lai (JIRA)" < >
  • To:
  • Subject: [jsr236-spec issues] [JIRA] Created: (CONCURRENCY_EE_SPEC-31) Inconsistency in ManagedTaskListener#taskAborted javadoc
  • Date: Thu, 23 May 2013 19:47:59 +0000 (UTC)
  • Auto-submitted: auto-generated

Inconsistency in ManagedTaskListener#taskAborted javadoc
--------------------------------------------------------

                 Key: CONCURRENCY_EE_SPEC-31
                 URL: https://java.net/jira/browse/CONCURRENCY_EE_SPEC-31
             Project: concurrency-ee-spec
          Issue Type: Bug
          Components: 1.0 Errata
    Affects Versions: 1.0
            Reporter: anthony.lai
            Assignee: anthony.lai


The following inconsistency in ManagedTaskListener JavaDoc regarding the 
ordering of taskAborted/taskDone notifications.

taskAborted method JavaDoc:
"This method may be called after taskDone()"

State Transition Diagram and examples B, C, D all show taskAborted happening 
BEFORE taskDone.

The sentence in the javadoc should be modified to

"This method may be called after taskSubmitted()"

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[jsr236-spec issues] [JIRA] Created: (CONCURRENCY_EE_SPEC-31) Inconsistency in ManagedTaskListener#taskAborted javadoc

anthony.lai (JIRA) 05/23/2013
 
 
Close
loading
Please Confirm
Close