For a plug-in to be available for YaTiSeWoBe, whichever type (see Section 3.3.1, “Types”) or level (see Section 3.3.2, “Levels”), it has to be created.

A plug-in is in the "create" state after it's constructor has return. If the constructor fails to return gracefully, the plug-in will not be available for the user.

Even a plug-in that has been in-activated by the user through the plug-in manager (Section 5.2.1, “Plug-in manager”), will go into this state. Therefor, no important resources should be acquired during construction.

The constructor is always called exactly once during a session.

A plug-in is in the "init" state after the call to it's void init(SharedProperties props) has returned gracefully.

The "init(SharedProperties)" function is called exactly once for active plug-ins during a session.

A plug-in is in the "start" state after the call to it's void start() has returned gracefully.

A plug-in can go from "start" to "stop" states many times during a session.

Figure 6.2. Window plug-in life cycle (partial)

Window plug-ins have a specific "start" state.

A plug-in is in the "stop" state after the call to it's void stop() has returned gracefully.

A plug-in can go from "start" to "stop" states many times during a session.

Before gracefully unloading the plug-ins, YaTiSeWoBe calls void destroy() on all active plug-ins to give them a chance to release cleanly their resources.

The "destroy()" function is called exactly once for active plug-ins during a session.