Page History: Root Object
Compare Page Revisions
Page Revision: 2010/10/12 14:58
When a workflow is created it can optionally be made a 'root' object. Making an object root prevents the garbage collector from reclaiming resources used by workflow, even if there are no references to the workflow. A 'root' object will exist forever, surviving program shutdowns.
It is practice in Jetfire programs to make long lived objects 'root' and not rely on references from another object such as collection. User objects are typically made 'root'.
All objects created directly by the application interface are automatically root.
Workflows created pro-grammatically, by default, are not root objects and will be reclaimed by the garbage collector if they have not reference.