Pluggable debugging interface for graphical notation diagrams
View Patent ↗A low-level process, which was mapped from a high-level graphical notation diagram, is debugged using the high-level graphical notation diagram. To debug the low-level process, a debugging interface allows a user to set and track breakpoints and other debug events from the high-level graphical notation diagram. When a breakpoint or other debug event is encountered during low-level processing, the high-level graphical notation diagram is updated to show the status of the low-level process.
1. A machine-implemented method for debugging a low-level process comprising:
obtaining a graphical notation diagram representing a specific function or feature in the low level process, wherein the graphical notation diagram comprises one or more graphical elements;
setting one or more high-level debug events on the one or more graphical elements in the graphical notation diagram;
converting the graphical notation diagram into low-level code after setting the one or more high-level debug events, wherein the low-level code comprises one or more low-level debug events corresponding to the one or more high-level debug events;
generating a set of pending event requests for the one or more high-level debug events, wherein the set of pending event requests are to listen for the one or more low-level debug events;
initiating execution of the low-level code to generate a low-level debug event;
detecting, during execution of the low-level code, an output of the low-level debug event;
comparing the output of the low-level debug event with the set of pending event requests including a specific event request;
matching the output of the low-level debug event to the specific event request; and
updating the graphical notation diagram with breakpoint state information in response to a positive matching result of the output to the specific event request,
wherein the graphical notation diagram is a business process modeling notation (BPMN) diagram, and
wherein the low-level process is a business process execution language (BPEL) process.
2. The machine implemented method of claim 1 , wherein updating the graphical notation diagram includes changing the appearance of a graphical element in the graphical notation diagram that is associated with the low-level debug event.
3. The machine-implemented method of claim 2 , wherein changing the appearance of the graphical element in the graphical notation diagram includes highlighting the graphical element in the graphical notation diagram that is associated with the low-level debug event.
4. The machine-implemented method of claim 1 , wherein updating the graphical notation diagram includes displaying a set of instructions from the low-level process.
5. The machine-implemented method of claim 1 , wherein the one or more high-level debug events includes at least one breakpoint.
6. The machine-implemented method of claim 5 , wherein the one or more low-level debug events include a breakpoint.
7. The machine-implemented method of claim 1 , wherein the one or more high level events includes a step event.
8. The machine-implemented method of claim 7 , wherein the one or more low-level debug events include a step event.
9. A machine-readable storage medium comprising instructions which, when executed by a processor, cause the processor to debug a low-level process by:
obtaining a graphical notation diagram representing a specific function or feature in the low-level process, wherein the graphical notation diagram comprises one or more graphical elements;
setting one or more high-level debug events on the one or more graphical elements in the graphical notation diagram;
converting the graphical notation diagram into low-level code after setting the one or more high-level debug event, wherein the low-level code comprises one or more low-level debug events corresponding to the one or more high-level debug events;
generating a set of pending event requests for the one or more high-level debug events, wherein the set of pending event requests are to listen for the one or more low-level debug events;
initiating execution of the low-level code to generate a low-level debug event;
detecting, during execution of the low-level code, an output of the low-level debug event;
comparing the output of the low-level debug event with the set of pending event request including a specific event request;
matching the output of the low-level debug event to the specific event request; and
updating the graphical notation diagram with breakpoint state information in response to a positive matching result of the output to the specific event request,
wherein the graphical notation diagram is a business process modeling notation (BPMN) diagram, and
wherein the low-level process is a business process execution language (BPEL) process.
10. The machine-readable storage medium of claim 9 , wherein the instructions for causing the processor to update the graphical notation diagram include instructions for causing the processor to change the appearance of a graphical element in the graphical notation diagram that is associated with the low-level debug event.
11. The machine-readable storage medium of claim 10 , wherein the instructions for causing the processor to change the appearance of the graphical element in the graphical notation diagram include instructions for causing the processor to highlight the graphical element in the graphical notation diagram that is associated with the low-level debug event.
12. The machine-readable storage medium of claim 9 , wherein the instructions for causing the processor to update the graphical notation diagram include instructions for causing the processor to display a set of instructions from the low-level process.
13. The machine-readable storage medium of claim 9 , wherein the one or more high-level debug events include at least one breakpoint.
14. The machine-readable storage medium of claim 13 , wherein the one or more low-level debug events include a breakpoint.
15. The machine-readable storage medium of claim 9 , wherein the one of more high level debug events include a step event.
16. The machine-readable storage medium of claim 15 , wherein the one or more low-level debug events include a step event.