[Hippo-cms7-user] can the reload on startup functionality be undone?
u.hommes at onehippo.com
Tue Dec 18 17:03:04 CET 2012
In both versions initialize items are determined to be reload-enabled
by reading the current value of the reload-on-startup property that is
in the hippoecm-extension.xml file at the time of bootstrapping. So if
the item is not there in that file when the system is bootstrapped
then no reloading is done. When the item is determined to be reload
enabled it still needs to have a newer version than the version that
was loaded previously in order to trigger an actual reload.
So to conclude: you can safely remove the initialize item from the
extension file and the fact that it is still registered in the
repository as a reloadable item is no problem.
On Tue, Dec 18, 2012 at 2:37 PM, Bert Leunis <b.leunis at onehippo.com> wrote:
> Hello all,
> We just brought a release to production using the new 'reload on startup'
> functionality . Since now the whole DTAP street has been changed, for the
> next release we can remove these reloadonstartup nodes from
> I noticed that a reload on startup marker is added to the
> hipposys:initialize nodes in the repository. Is it so that the action I
> described above is in vain? Will the reload stop when I remove it from
> hippoecm-extension.xml or will it keep reloading at every startup because
> the flag for that is stored in the initialize nodes?
> With kind regards/Met vriendelijke groet,
> Bert Leunis
> Amsterdam - Oosteinde 11, 1017 WT Amsterdam
> Boston - 1 Broadway, Cambridge, MA 02142
> US +1 877 414 4776 (toll free)
> Europe +31(0)20 522 4466
> Hippo-cms7-user mailing list and forums
More information about the Hippo-cms7-user