Author: rexx77
Subject: Bind plan as a member to another bind plan
Posted: Thu Feb 16, 2017 2:02 am (GMT 5.5)
Folks,
Application A, B, C and D calls another application's routing module (Common 1 - Name of the module) and this Common1 module calls couple of other common routines to post the updates/inserts passed from different applications. So far the going was good and Common1 application never added any new common routines in the call flow, but now due to recent regulatory requirement, Call chain from Common1 has been modified to include couple of new common routines. This resulted in requesting Application A, B, C and D to rebind their packages to include the new common modules.
I suspect in another few months there will be one or two more new common routines will be added to the call chain from Common1, I am just exploring the ideas/ways to make the Application A, B, C and D life simple, not sure whether they have any other easy way not to rebind their BIND PLANS when ever new common module is added in the call chain. Do you guys aware of any other alternatives?
PS: Common1 application has some rules in putting the logic in separate modules, so option of having all new logic in one module is ruled out.
Subject: Bind plan as a member to another bind plan
Posted: Thu Feb 16, 2017 2:02 am (GMT 5.5)
Folks,
Application A, B, C and D calls another application's routing module (Common 1 - Name of the module) and this Common1 module calls couple of other common routines to post the updates/inserts passed from different applications. So far the going was good and Common1 application never added any new common routines in the call flow, but now due to recent regulatory requirement, Call chain from Common1 has been modified to include couple of new common routines. This resulted in requesting Application A, B, C and D to rebind their packages to include the new common modules.
I suspect in another few months there will be one or two more new common routines will be added to the call chain from Common1, I am just exploring the ideas/ways to make the Application A, B, C and D life simple, not sure whether they have any other easy way not to rebind their BIND PLANS when ever new common module is added in the call chain. Do you guys aware of any other alternatives?
PS: Common1 application has some rules in putting the logic in separate modules, so option of having all new logic in one module is ruled out.