Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.1.1
-
Fix Version/s: 1.4.0
-
Component/s: Process service
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Critical [ 2 ] |
| Fix Version/s | 1.2.0 [ 10870 ] |
| Fix Version/s | 1.1.2 [ 10927 ] | |
| Fix Version/s | 1.2.0 [ 10870 ] |
| Comment | [ Merged in branch petals-se-flowable-1.1.x ] |
| Fix Version/s | 1.2.0 [ 10870 ] | |
| Fix Version/s | 1.1.2 [ 10927 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|

On error, InOnly service provider invocation must be put as dead letter.
It's seems that for CXF stack, for MEP InOnly, no error occurs on remote side.
Perhaps, a workaround must be done invoking the service provider synchronously: on status 'error', an exception could be thrown.