2.3.4 Lifecycle of I/O Plugin instances
The following describes the lifecycle of plugin instances.
- Organization of this subsection
(1) Creating and retaining I/O Plugin instances
For I/O Plugins having the same plugin ID, one instance is retained in one window. The instances are retained in HTTP sessions based on window IDs as keys. The following figure shows instances of I/O Plugins.
When you execute I/O Plugins, instances of the I/O Plugins to be executed are acquired from HTTP sessions by using window IDs and plugin IDs as keys. If an instance cannot be acquired from HTTP sessions, new instances are created and then added to the HTTP sessions. At this time, only the instances to be executed are created. The figure below shows an example of Operational Content containing branch nodes. If transition occurs from node 1 to node 2, and to node 4 during execution of this Operational Content, plugins A, B, and D are executed but plugin C is not. Therefore, if operation of Operational Content containing this transition is executed, an instance of plugin C is not created.
(2) Discarding I/O Plugin instances
The table below indicates when I/O Plugin instances are discarded. This applies regardless of whether the operation is performed in the Operational Content Execution Window or Operational Content Execution Window (preview).
No. |
Discarded when: |
Plugin instance to be discarded |
---|---|---|
1 |
Operational Content is displayed in the Operational Content Execution Window or Operational Content Execution Window (preview)#1 |
Instances retained by the HTTP session (when the operation is performed) based on the window ID of the window in which the operation is performed |
2 |
The Editing Window View menu is clicked |
|
3 |
The Close button is clicked#2 |
|
4 |
The Done button is clicked#3 |
|
5 |
The Logout button is clicked |
All instances retained by the HTTP session to be discarded |
6 |
A session times out |