The EAR loads the WAR, whose sole purpose is to catch the initialization
of itself so it can register the PostgreSQL pool implementation.

Another WAR will be created that relies on that initialization, and which
provides the web pages for a generic backing store.

This application WAR will then be wired to the EAR as well.  In theory,
the EAR will get booted on server startup, launching both WARs, one of which
initializes the database schema pool.

If it all pans out, I should have access to a backing store cached instance
by the end of the week.  Maybe sooner.