anonymous wrote :
| I think, perhaps, my first post was a bit too abstract to be clear. So... here is a
more concrete example.
|
Thanks, that always helps
anonymous wrote : E(mail) will provide J(bpm) with delivery notification and read receipt
information via http callbacks.
| I hope it is an internal emailing system where users have no control over whether or
not they send de read notification.
anonymous wrote : think that you are saying that I could model this in a different way,
using tokens to ensure that the two async events are handled correctly (i.e. thread J2
will signal the "delivery" token and thread J3 will signal the "read"
token. For example:
|
|
|
| |
| | start
| | |
| | |
| | V
| | send email via http
| | |
| | |
| | V
| | +------------------fork------------------+
| | | |
| | V V
| | wait for delivery receipt wait for read receipt
| | | |
| | | |
| | V V
| | send delivery receipt via http send read receipt via http
| | | |
| | | |
| | +------------------join------------------+
| | |
| | |
| | V
| | end
| |
|
| Have I understood you correctly?
Yes, and if you want to prevent de read-receipt being send to the P system before or at
the same time as the delivery-receipt, you could also model it like this
| start
| |
| |
| V
| send email via http
| |
| |
| V
| +------------------fork------------------+
| | |
| V V
| wait for delivery receipt wait for read receipt
| | |
| | |
| V |
| send delivery receipt via http |
| | |
| | |
| +------------------join------------------+
| |
| |
| send read receipt via http
| |
| |
| V
| end
|
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197570#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...