E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (7)
View Page History
...
h1. Introduction Several concurrent life-cycles exist in Petals ESB:
* the Petals ESB life-cycle,
* the share-library life-cycle,
* the component life-cycle,
* the service-assembly life-cycle,
* the service-unit life-cyle.
* the share-library life-cycle,
* the component life-cycle,
* the service-assembly life-cycle,
* the service-unit life-cyle.
* [the Petals ESB life-cycle|#petals-esb-lifecycle],
* [the shared-library life-cycle|#sharedlibrary-lifecycle],
* [the component life-cycle|#component-lifecycle],
* [the service-assembly life-cycle|#service-assembly-lifecycle],
* [the service-unit life-cyle|#service-unit-lifecycle].
* [the shared-library life-cycle|#sharedlibrary-lifecycle],
* [the component life-cycle|#component-lifecycle],
* [the service-assembly life-cycle|#service-assembly-lifecycle],
* [the service-unit life-cyle|#service-unit-lifecycle].
{column}
...{section}
{anchor:petals-esb-lifecycle}
h1. The Petals ESB life-cyle
...It contains only one state: STARTED. The implicit state 'STOPPED' does not really exist because in such state no Petals ESB process is running.
The transition from state 'STOPPED' to 'STARTED' is realized using the Petals ESB startup script '{{petals-esb}}'. The return to the state 'STOPPED' is realized using {{^C}} or the command '{{petals-esb stop}}'. See [Starting and stopping Petals ESB])
{anchor:sharedlibrary-lifecycle}
{anchor:sharedlibrary-lifecycle}
h1. The shared-library life-cyle
...It contains only one state: INSTALLED. The implicit state 'UNINSTALLED' does not really exist because the shared-library is not instantiated or loaded.
{anchor:component-lifecycle}
h1. The component life-cycle
{anchor:service-assembly-lifecycle}
h1. The service-assembly life-cycle
{anchor:service-unit-lifecycle}
h1. The service-unit life-cyle