Hi Danny Trunk, Could you please share the use case why you need a service call stack?
If you share the use case it may be possible you will get a better answer. Kind Regards, Deepak Dixit DIRECTOR OF PRODUCT ENGINEERING mobile: +91 9826754548 email: deepak.di...@hotwax.co *www.hotwax.co <http://www.hotwax.co/>* On Thu, Feb 4, 2021 at 8:40 PM Danny Trunk <d...@zyres.com> wrote: > Hello, > > let's imagine Service A is calling Service B directly through > dispatcher.runSync and Service C is running as an SECA action of Service B. > The call stack would be: Service A -> Service B -> Service C (through SECA) > > Or let's imagine Service D is running as an EECA action of entity Product. > The call stack would be: Product Entity -> Service D (through EECA) > > Is it possible to get that information somehow? > I can't find anything helpful in DispatchContext or GenericDispatcher. > > Output into a log file would be great. > > Kind regards > Danny. >
