You can apply a pattern you have designed in a runtime instance of the developer workbench to test for errors. Errors are reported back to the Console view of the developer workbench.
Before you test a pattern, you can add debug messages to the hot spots to trace the process sequence for expansion and update methods. Trace messages are displayed in the developer workbench Console view. The pattern cheat sheet, Authoring Patterns, provides detailed examples of how add debug messages. You open the cheat sheets from the Help menu.
If you included breakpoints in your pattern code; they are listed and controlled in the Breakpoint view in the developer workbench. You can resume pattern processing after a reaching a breakpoint by clicking
.For details on applying patterns, refer to the topics on applying patterns. As every pattern is unique, there is no single method to test patterns. The following instructions are options to modify the pattern. Parameters with dependencies invoke multiple methods for each command when a change occurs to a supplier parameter.
Parent topic: Testing patterns
Previous topic: Starting a run time debug workbench
Related concepts
IBM Rational design patterns
Pattern code and support files
Pattern instantiations
Related information
Displaying available patterns
Creating pattern instances
Specifying arguments for pattern instances
Exporting RAS assets