fail gracefully

[alan-stokes]

Hi All.

I was having a demo with Dan this morning and there came a question which I couldn't answer right say, and my gut instinct is that its not been developed yet. So here goes my understanding of the state of play and the impacts.

1. the back-end when booted up adds a set of default users, and 1 proposal called "observing the stars"
2. when the back end is rebooted during changes to the back end, anything outside 1s scope is lost.
3. there is ui support for adding new users to the database and new proposals (obviously).
4. that there is no logic for retaining these users / proposals when the back end is shut down in any fashion?

so is this logic solid? or is there support that needs to be triggered in a specific way to ensure users and proposals are retained between boots?

[alan-stokes]

if not. is this something we should be considering?

[AllanEngland]

This is the behaviour we wanted for developing, but obviously not production. I think you can change how it works in AppLifecycleBean.java in the API project if you want to tweak it, however I understand that we will have a proper production version available at some point.