Hi all,

This is a follow up to my previous question about dealing with
unwanted
resumable messaging instances. Here is what I need to do: I need to
send a
request to a web service in my orchestration (this is being done
through a
request-response port). I wish to do this within a scope shape, so
that if
any of the error conditions that I am watching out for arise, I can
deal with
it appropriately. Once I have handled the exception in the
orchestration, I
do not want to do anything else.

In regards to the above, I have a few questions:

1. What are the implications of setting the Transaction Type (for both
the
orchestration and the scope shape) to none?

2. While I played around with an orchestration designed as described
above,
I noticed that despite the exception being caught and handled, I get
resumable messaging instances in HAT (where the messaging instances
are the
web service requests, that were already received by the web service).
Why
does this happen? Would it have to do anything with a response not
being
received from the web service?

3. If the resumable messaging instances mentioned in 2 do occur
because of
the response not being received, and I don't really care about the
response,
is there a way to do away with the messaging instances automatically
without
me having to go to HAT to terminate them? Is there another way to
design the
orchestration to deal with unreceived responses?

Any help with these questions will be much appreciated.

Thanks.

[ Post a follow-up to this message ]