Version 8.2 (2013-03-18)
 —  Special Development Topics  —

How Things End

This document covers the following topics:


End of an Application Designer Session

A session normally ends if the page which was opened with the StartCISPage servlet is closed. This happens for example:

In other words: the session is normally kept alive as long as the user stays in the Application Designer environment.

Why "normally"? If a session is without user interaction for a long time, the session is timed out on the server side. When the user comes back to continue interaction, a corresponding message appears. The duration until a session is timed out is configurable; see the description of the cisconfig.xml file in the Configuration documentation for details.

If a session ends, all its subsessions and all adapters in the subsessions are automatically ended.

Top of page

End of an Application Designer Subsession

A subsession is ended via an API. There are two APIs available:

For further information, see the JavaDoc documentation.

Top of page

End of an Application Designer Adapter

Adapters typically stay alive until the subsession ends in which they are living. There is also an API available to directly end adapters:

Top of page