public interface SubprocessManager extends RuntimeManager, SubInstanceStateListener
From the point of view of an execution manager a subprocess manager is a
runtime manager executing (LWP-)activities. So the SubprocessManager has to
implement the methods defined for RuntimeManagers in general, i. e. it must
implement the methods defined in RuntimeManager. Since the subprocess
manager does not need to support multiple users,
RuntimeManager.logon(de.aristaflow.adept2.base.sessionmanagement.SessionToken, de.aristaflow.adept2.base.sessionmanagement.ClientSessionFactory),
RuntimeManager.updateClientSessionFactory(de.aristaflow.adept2.base.sessionmanagement.SessionToken, de.aristaflow.adept2.base.sessionmanagement.ClientSessionFactory),
and
RuntimeManager.logoffAndTerminateActivities(de.aristaflow.adept2.base.sessionmanagement.SessionToken, de.aristaflow.adept2.base.sessionmanagement.QualifiedAgent, boolean)
do not need to be supported, implementations may be empty.
In order to be able to be notified about subprocess termination events by the
execution manager executing the subprocess instance, the SubprocessManager
must provide the callback methods defined by the
SubInstanceStateNotification
interface.
commit, getExecutionControlManager, getSynchronousActivityStarting, logoffAndTerminateActivities, logon, preferAutoStartNotification, prepareCommit, resumeActivity, rollbackActivity, startActivity, updateClientSessionFactorygetSubInstanceStateNotificationgetLocalUris, getRelease, getRuntimeRequiredServices, getServiceInstanceName, getStartupRequiredServices, getURIs, init, ping, preShutdown, shutdown, start