|
From: Zoran K. <zo...@fu...> - 2007-10-04 08:31:11
|
> It did not require any configuration? Does that mean it uses an included > database? > > > I think so. It comes as a complete package with tomcat and everything > included. I can't remember doing anything else than unpacking it and > starting it up. Users are configured through the webinterface. Hmm, lets have a go with that kind of deploy next time too. As an additional download package. Should not be too much work than packaging and testing it. > Yup, that would be the next step. I'm already working a bit to get the > initialization process somewhat more transparent. After that I was > thinking about using an embedded meta-database like hsqldb or apache > derby to store the details about the real database in. That way we can > configure everything from a webinterface and be done with it. Nice! > The only thing requiring manual configuration would be the container > specific authorization details if you would want to use that. One issue > though would be the database drivers as these would then be required in > the classpath of the webapp (although we could give an > upload/path_to_jar option and then load it with the pluginclassloader). Or include a couple of the most widely used drivers by default. Lets not spend too much time now making it easier to support every database. If we support a meta-db one out of the box, and e.g. mysql/postgres through configuration wizard, that would already be great. |