Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistency in ManagedTaskListener#taskAborted javadoc #31

Open
glassfishrobot opened this issue May 23, 2013 · 3 comments
Open

Inconsistency in ManagedTaskListener#taskAborted javadoc #31

glassfishrobot opened this issue May 23, 2013 · 3 comments

Comments

@glassfishrobot
Copy link

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()"

Affected Versions

[1.0]

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Reported by alai8

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
This issue was imported from java.net JIRA CONCURRENCY_EE_SPEC-31

@glassfishrobot
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant