Posted: Sun Oct 23, 2016 5:29 am Post subject: Shared Library Error Handling
Newbie
Joined: 23 Oct 2016 Posts: 1
Hello Experts,
On our current project we have implemented error handling in static library due to few advantage with shared library we have moved for the same. Now we are seeing weird issue when ever there is a web service cal [example HTTP Request ]which ends with error terminal that would enter common error handler will still proceed for next operations after entering conman handler , If we go with static library flow terminates after reaching conman error handler as it has come from error terminal and this is expected. Not sure why flow continue for next calls when we use shared library. Just difference here is static and shared library. Code wise everything same.
Have you run a user trace for both scenarios to see if you can spot any obvious differences ? _________________ Independent Middleware Consultant
andy@knownentity.com
What fix pack level of IIB V10 are you at?
In 10.0.0.5 and 10.0.0.6 fixes were made on how a subflow (and its nodes) calculate whether the calling subflow nodes terminals are connected or not. Moving a subflow from a static library to shared library might change the preparation order of the nodes and as such before these issues were fixed might give the wrong result. _________________ Regards
Craig
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