com.ibm.websphere.asynchbeans
Interface WorkEvent
- public interface WorkEvent
Field Summary
Modifier and Type | Field and Description |
---|---|
|
WORK_ACCEPTED
The
WORK_ACCEPTED constant indicates Work was successfully submitted to
the WorkManager.
|
|
WORK_COMPLETED
The
WORK_COMPLETED constant indicates the Work completed.
|
|
WORK_REJECTED
The
WORK_REJECTED constant indicates Work.run failed to start.
|
|
WORK_STARTED
The
WORK_STARTED constant indicates the Work was allocated to a thread
and is about to execute.
|
Method Summary
Modifier and Type | Method and Description |
---|---|
getException()
This returns the exception if any in the case of WORK_COMPLETED.
|
|
|
getStartDuration()
This returns 0 in the current implementation.
|
|
getType()
This returns WORK_ACCEPTED etc
|
getWork()
This returns a copy of the Work in progress.
|
Field Detail
WORK_ACCEPTED
- static final int WORK_ACCEPTED
See Also:
WORK_REJECTED
- static final int WORK_REJECTED
The
WORK_REJECTED
constant indicates Work.run failed to start.
This can happen anywhere during the start process. It happens independently of all
other events. Work might be rejected due to the startTimeout expiring,
context propogation failure, security failure, or other internal failures.
See Also:
WORK_STARTED
- static final int WORK_STARTED
The
WORK_STARTED
constant indicates the Work was allocated to a thread
and is about to execute.
See Also:
WORK_COMPLETED
- static final int WORK_COMPLETED
The
WORK_COMPLETED
constant indicates the Work completed. The Work might
have completed successfully or with error.
See Also:
Method Detail
getType
- int getType()
This returns WORK_ACCEPTED etc
getWork
- Work getWork()
This returns a copy of the Work in progress.
getStartDuration
- long getStartDuration()
This returns 0 in the current implementation.
getException
- WorkException getException()
This returns the exception if any in the case of WORK_COMPLETED.
WORK_ACCEPTED
constant indicates Work was successfully submitted to the WorkManager. This means the parameters and thread context are valid at this point. It does not reflect acceptance to a pool or successful thread allocation.