Index Changes

Difference between version and version     

Back to M Eprocessing And Property Propagation, or M Eprocessing And Property Propagation Info


At line 2 added 3 lines.
Business Process execution behavior is enumerated by Message Exchange type.
At line 28 changed 3 lines.
When InOut (two way request ) message creates an instance.
Model - A - The time interval between the execution of Receive and Reply is unpredictable and could take long.__It is default behavior.__
Model - B - The time interval between the execution of Receive and Reply is predictable and short.
When InOut (two way request ) message creates an instance.
At line 32 changed 1 line.
Response/Fault is sent on execution of associated "Reply" activity.
"Reply" activity in Business Process definition determines when the response/fault is set on Message Exchange and this attribute does not determine timing of it.
At line 34 changed 1 line.
Model - A
\\
atomic=no is default behavior.__
\\
At line 36 removed 2 lines.
* There is potential for duplicate message if system crashes and consumer/partner redelivers the message.
* Duplicate messages can be addressed by enabling BPEL-SE persistence and tagging the Message with unique id. It is semantically "once-only-once".
At line 39 changed 1 line.
Model - B
!atomic=no
At line 41 changed 2 lines.
* There is potential for duplicate message if system crashes and consumer/partner redelivers the message.
* Duplicate messages can be addressed by associating transaction with the Message. No need to persist the state of the business process until execution of Reply activity. State of BP at Reply activity is persisted in the message's transaction.
*It is preferred option when the time interval between the execution of Receive and Reply is unpredictable and could take long.
*There is potential for duplicate message if system crashes and consumer/partner redelivers the message.
*Duplicate messages can be addressed by enabling BPEL-SE persistence and tagging the Message with unique id. It is semantically "once-only-once".
At line 46 added 5 lines.
!atomic=yes
*IT is preferred option when the time interval between the execution of Receive and Reply is predictable and short.
*There is potential for duplicate message if system crashes and consumer/partner redelivers the message.
*Duplicate messages can be addressed by associating transaction with the Message. No need to persist the state of the business process until execution of Reply activity. State of BP at Reply activity is persisted in the message's transaction.

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-29) was last changed on 18-Nov-08 16:16 PM, -0800 by Murali