Posted: Mon Oct 28, 2002 7:00 pm Post subject: best practice
Centurion
Joined: 25 Jun 2002 Posts: 144
hello all,
Lets take compute node as an example.
-> compute (Out) -> output node
above would be fine in the perfect world scenario.
But if exception occurs then message will be sent on failure path of compute node.
In my case message is immaterial if it takes exception path, so is it a GOOD practice to leave Exception path un-connected ? Any idea what impact it causes to broker or dfe.
Am against of this idea because - never exit the program abruptly .. and always catch exception.
If the failure terminal is not connected, then the exception will cause the message to rollback all the way to your try-catch node or your input node.
The reason for the existence of the failure terminal is so that when exception occurs at different points of the message flow, you can have different failure-handling methods at those different points.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum