On 6/22/05, Hans Gerwitz <hans(a)phobia.com> wrote:
+1
...but the subject of your message was misleading. This is using a
container managed source FOR hibernate, rather than "instead of", no?
yes & no :) basically, with the current config we let hibernate create
and manage the DBCP pool. Thus the "instead of", which was misleading
anyway :)
Has there been a discussion in the past of how
application configuration
generally is stored? Playing with installing XWiki here-and-there, I find
myself missing the way SnipSnap stored configuration within the data store
(XWiki, after all, already does in the XWiki space, yet some configuration
is "outside" in xwiki.cfg). An option, at least, to use e.g.
XWiki.ApplicationProperties would be welcome.
i agree. I recently had to install atlassian's jira on
xwiki.org and
was really pleased with the way it is packaged and configured. You
just had to edit tomcat's config to setup a container managed
datasource, then use the application itself to configure it.
While I'm griping about the installation process, it'd be nifty if the app
"bootstrapped" by creating the DB itself when configured with an empty data
store.
I guess there is much more to do than just creating tables, a really
tedious task IMHO, so i guess the developper who'll volunteer for that
will get tons of karma points :)
Erwan