Petals Documentation > Petals ESB > Petals ESB 5.4.0 > Page Comparison - Petals ESB lifecycles (v.4 vs v.5)

Petals ESB lifecycles

Version 4 by Christophe DENEUX
on Sep 22, 2014 17:05.
<< Changes from 3 to 4
compared with
Version 5 by Christophe DENEUX
on Sep 22, 2014 17:23.
Changes from 5 to 6 >>
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
...
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}
...
{gliffy:name=Shared-Library lifecyle|version=3}
It contains only one state: INSTALLED. The implicit state 'UNINSTALLED' does not really exist because the shared-library is not instantiated or loaded.
The transition from state 'UNINSTALLED' to 'INSTALLED' is realized installing the shared library, and the return to the state 'UNINSTALLED' is realized uninstalling the shared-library. A shared library can be (un)installed using [Petals CLI|Command Line Interface], [the Petals Autoloader|Petals ESB "Autoloader"] or the JMX API.

{anchor:component-lifecycle}
...