Developing Actions

Retired Content
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Actions are atomic units of work called by recipes in a defined sequence. The sequence is specified in the recipe definition. An action accepts input, from either arguments that have been gathered by the calling recipes or output from an action executed earlier in the sequence. Recipe actions are specified in the recipe definition, with the Recipe Framework calling the actions in the order specified in the Guidance Package configuration file.

This section illustrates how to write your own action classes, and it discusses the circumstances under which the Recipe Framework will raise exceptions if actions are not implemented correctly. It also gives examples of different actions that you can use in conjunction with your recipes and it describes two extension points in the framework that allow implementing complex action execution patterns.

See also

Writing Action Classes | Raising Exceptions | Obtaining and Using Host Services | Action Coordination Extensibility