When debugging a consumer eSpace that references a producer eSpace to reuse some of its functionality, two situations can occur:
Debug the Consumer eSpace
In this case we want to solely debug the consumer eSpace. We do not need to debug the functionality reused from the producer eSpace.
For this, just follow the same steps as for debugging an eSpace without references. See more in Debug an eSpace.
All functionality that is reused from the producer eSpace is treated as a black-box, meaning that:
You cannot step into and debug inside the reused functionality;
You only can inspect the values sent to the reused functionality and the values returned by it.
Debug the Producer eSpace
In this case, when in the consumer eSpace, we want to debug the functionality that is being reused from the producer eSpace.
For this, proceed as follows:
In the producer eSpace:
Open the 'Debugger' menu and choose the Select Entry eSpace... option;
Choose the consumer eSpace from the list;
Place breakpoint(s) where you want the execution to stop;
Start the debugger in the 'Debugger' menu:
Choose Run an eSpace to debug in the Personal Area;
Choose Debug in the Public Area to debug in the Public Area.
Learn how to Debug in Public and Personal Areas.
In the consumer eSpace:
Execute the application and use it;
The debugger will not stop in any breakpoint in the consumer eSpace;
When the reused functionality is executed, the debugger stops at the breakpoint(s) in the producer eSpace.
Conditions for an Entry eSpace
There are some important conditions for a consumer eSpace listed as an Entry eSpace:
It must be a consumer of the producer eSpace, i.e., it (directly or indirectly) references your eSpace;
It must be up-to-date with the producer eSpace, i.e., its reference is refreshed;
You must have permissions to Publish it.
Debug an eSpace