geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <>
Subject Re: [jira] Created: (GERONIMO-706) Remove axion from Geronimo assembly and remove default-database-plan.xml
Date Tue, 05 Jul 2005 20:14:34 GMT
	We should think about whether we want to distribute Geronimo with 
configurations like this installed, or just with plans you can customize 
and install yourself.  For example, it would be nice to have a directory 
of JDBC plans for many major databases, but I don't think it would be such 
a good idea to have them all installed into the server.  I guess an 
embedded product like Derby might be an exception (if no 
username/password/schema customization is required).

	But generally I'd prefer to distribute a clean server, with
perhaps a "samples" directory and a script to install the plans for some
or all of the samples.  So it starts totally clean (no databases, JMS
destinations, sample apps, etc.  besides what's required by the server and
a management console) but there's a single command to throw all the
samples in if you like.


On Tue, 5 Jul 2005, Jeremy Boynes wrote:
> When I added SystemDatabase I kept the DefaultDatabase plan around 
> purely to avoid issues with installations at the time - back then Derby 
> had not produced even an unofficial release from the incubator.
> We have been trying to encourage people to use Derby for nearly a year 
> now. I think it is time to finally kill off axion and replace it with 
> just Derby.
> We should keep the DefaultDatabase datasource around and separate from 
> the system one - I would suggest as another database in the same 
> instance. One is intended to be used by applications, the other just by 
> the system itself.
> --
> Jeremy
> Jacek Laskowski wrote:
> > wrote:
> > 
> >> a) Keep it and change it to use Derby rather than axion, so it is 
> >> available for Demo applications etc?
> > 
> > 
> > I like the default-database-plan.xml which tells you what default 
> > database Geronimo is tested against. Then, others dbs could have their 
> > own plans with the name name-version-database-plan.xml.
> > 
> >> c) Remove it and enhance the izpack installer to enable the user to 
> >> create a new database, prompting the user for a database name and a 
> >> configuration Id to give to the generated plan.  The downside to this 
> >> is that users probably won't be thinking this far ahead (about 
> >> databases) when installing Geronimo.
> > 
> > 
> > Instead of removing it, it'd be better off just enhancing the izpack 
> > installer. So, before asking a user for details, it would ask if (s)he 
> > wants to change anything in the default db configuration.
> > 
> > Jacek
> > 

View raw message