public static final class Backend.Builder

Registers this server’s websocket endpoints when it starts.

Called once, before the listener accepts anything, so there is no window in which a route exists in the application’s mind and not in the server’s – which is what a websocket(path, endpoint) setter on a started server left open.

Terminates TLS with this certificate and key.

Drops a context given to the other overload earlier, because resolveTls answers from the context FIRST: without this, a builder configured conditionally kept serving the old certificate and this call did nothing at all – silently, which is the part that matters, since an obsolete certificate looks like a working server until it expires. The last TLS choice wins, as it does for every other setter here.

Only when something is actually supplied. tls(null, null) is not a way to turn a context off; it would make an argument nobody meant as a choice erase one that was.

Terminates TLS with a context the caller built.

Drops paths given to the other overload earlier, for the reason stated there, and on the same terms: a null context is not a choice and erases nothing.

The database, as a SQLite path or a postgres:// or mysql:// URL.

Drops a pool given to the other overload earlier: openDataSource answers from the pool FIRST, so without this a builder configured conditionally kept the earlier pool and this call was ignored – which is a server reading and WRITING to the wrong database while its configuration says otherwise. The last choice wins.

Ownership follows the same rule and stays correct either way: the builder opens this URL itself and therefore closes it, while a pool handed in belongs to the caller.

A pool the caller opened. It is closed when this server stops.

Drops a URL given to the other overload earlier, for the reason stated there. A null pool is not a choice and erases nothing.

Says that the handlers this server builds need a database, so one is opened even when nothing else asks for it.

The generated entry point calls this when any controller declares a constructor taking a DataSource or an EntityManager. Without it, a controller that declares a database dependency, has no entities behind it, and runs on a development profile with no URL configured was refused at start-up by requireDataSource – whose message suggests running on a development profile, which is what was already happening.

The alternative was to open the development default whenever the profile allows it. That is the wrong fix: it would give a database to every server that has no use for one, which contradicts “a server with no database opens none” and costs a file handle to prove it. What was actually missing is that a DECLARED dependency did not drive the decision, and the build knows exactly which controllers declare one.