Posted: Thu May 12, 2005 11:38 pm Post subject: Throw Nodes : Issues in maintaining exception info
Newbie
Joined: 12 May 2005 Posts: 1
Hi All,
I basically have a scenario in which 1 throw node is coming in the way of the other.The problem i am facing is when an error occurs in one of the lower subflows(Subflow A) i have a throw node in which i am setting the error code and error text.
Now, while it is propogating back towards the main subflow it is encountering another subflow that has(Subflow B) a throw node which has another value and the error text set as blank.Just before putting the message into the failure queue we log the error related information in a file.So what's happening is that this file always seems to be showing that an error occured in the Subflow B even if it has occured somewhere later like in subflow A and the error text and error code seems to be picked up from subflow B.
Could you please advise on what would be an ideal way to handle this situation . Also, are there certain thumbrules that need to be followed during the design of this type of 'exception ladders' i.e should we have landed into this situation in the first place ?
Thanks And Best Regards,
V _________________ What i would give now for one of them pangalactic gargleblasters
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