Please fall back to 404 everything when the data source is null.

[ydahhrk]

To be honest, the installation process is a huge mess, despite the demo. There are too many steps and little to no positive reinforcement between them.

One thing that would help tremendously would be the ability to start the server with no database. If the server does not find a data source in the context, it should fall back to not respond any objects but still provide simple echoes such as an index page and the help response. Currently, it throws an exception (which is, as a matter of fact, invisible to Tomcat logs by default) and refuses to start.

As it is, I'm finding myself driven to fuse several documentation pages (1 2 3) because they are in fact one single massive atomic step, and their separation feels rather misleading and unjustified.

[ydahhrk]

The 404 strategy wasn't actually implemented because the installation process got much simpler and also the SQL provider (which manages the datasource) is not even part of it anymore.

This might need to be reviewed when the SQL is brought back but, since by that point some other solution might be more sensible, I don't think there is a point in keeping this issue open.