22 Jun
2005
22 Jun
'05
4:28 p.m.
+1
...but the subject of your message was misleading. This is using a
container managed source FOR hibernate, rather than "instead of", no?
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.
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.
- - -
Hans Gerwitz
http://phobia.com/
On Jun 22, 2005, at 8:32 AM, Erwan Arzur wrote:
Hello,
Today, while installing xwiki on my own box, i've found very tedious
having to edit a file in a tomcat working directory (webapps/xwiki,
for instance) to change the database parameters.
Having a datasource defined in the container will allow admins to
avoid having to learn the internals of the application, and this is
how it's done in other apps like jira or confluence.
For tomcat, I feel it would be better to :
- make sure hibernate.cfg.xml refers to a datasource named "jdbc/
XWikiDS"
- define the said DataSource in $CATALINA_HOME/Catalina/localhost/
xwiki.xml
- put the jdbc driver in $CATALINA_HOME/common/lib, now that the
container is responsible for opening the connection
I think it will also ease the packaging of a standalone xwiki server.
What do you think ?
I'm attaching the configuration that worked for me almost out of
the box.
Erwan
<xwiki.xml>
<hibernate.cfg.xml>
--
You receive this message as a subscriber of the xwiki-
dev(a)objectweb.org mailing list.
To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/
wws