What if we ship an implementation of the new interceptor method that
iteratively calls the old interceptor method from the registered
interceptors? This way the changes to the core will be done and deprecated
old method is only invoked from new interceptor; easier to disable it in a
running system
On Fri, Nov 1, 2019 at 4:38 PM Gayashan Bombuwala
wrote:
> Hi Johann,
>
> Both the new handler and the old handler will be called at the end[1] of
> deleteServiceProvider() execution.
> By the time that postDeleteHandler gets executed, the relevant Service
> Provider object will been already
Hi Johann,
Both the new handler and the old handler will be called at the end[1] of
deleteServiceProvider() execution.
By the time that postDeleteHandler gets executed, the relevant Service
Provider object will been already removed. Hence, we can't read the Service
Provider object based on the
Hi Gayashan,
Though you introduce the method in the API, who calls the method? Now that
there are two methods is the ApplicationMgtService going to call both the
methods? Can't we read the Service Provider object based on the name rather
than introducing a new method for it?
Regards,
Johann.
On
Hi all,
Currently implementation of the postDeleteHandler[1] of
ApplicationMgtListener only accepts the name of the service provider as a
parameter. However the postCreateHandler[2] and postUpdateHandler[3] of the
ApplicationMgtListener accepts the relevant Service Provider object as a
parameter
