Of course you can also use all the normal ABAP tools - like runtime trace, SQL trace, memory snapshots, etc.
A general note - Cross Component Context binding is very expensive from a performance standpoint. Unlike context binding within one component, you aren't using a single shared set of data. For each component, the context must be copied in memory. Also there are sync operations to keep the contexts aligned. This is especially costly for large context nodes.
You should keep your cross component context binding to a minimal. Instead consider the usage of a class that has static attributes. You can build a class constructor to intialize the attributes and return a static instance of itself for all components that want access.
I'm in the process of creating a Web Dypnro ABAP Performance eLearning series right now. One of the episodes will focus on this very point - cross component context binding vs. a single shared class with static attributes. The performance benefits of the latter can be quite substantial.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.