Hi All,
I have a user question regarding the differences between try / catch and
onException
In sample documentation you find the use of
<try>
<to ../>
<catch>
<exception>foo.Exception</exception>
.. handle ..
</catch>
</try>
My question is, what are the logical differences between this and
<onException ..> and why would you use either ?
I ask this as I have a found two potential bugs, to which I want to provide
a correct patch for also (a "forced learn the code" task) but want to first
understand what each path is designed for.
*I suspect the onException will have something to do with managing
redeliveries etc.
*Logging the bugs shortly.*
[File poller throwing exception is not caught by onException
"before any messages are sent"] Use an Access Denial on a file (list but
not read, windows readlock etc)
[File poller does not "start" if wrapped in a <try> <catch>] *Are
there other endpoints that suffer the same, or is it incorrect use?
*
**
*cheers
r.
