Step APIs

One of the goals of JAFPL is to conceal as much of the underlying framework as possible from step implementors. Atomic steps are only required to implement an API; almost nothing about the framework is exposed. (Containers are a little trickier; there aren’t any provisions for extension containers at the moment, but I’m open to suggestions for new containers.)

The API for atomic steps is straightforward. Each step implmentation must implement the Step interface.

Most of the interface is completely straightforward:

That leaves only a few odds and ends.