On Tue, Sep 9, 2008 at 12:00 PM, Paul Pepper <[EMAIL PROTECTED]> wrote: > My questions relate to the article, "Database Profiles in AppFuse 2.0" > (http://raibledesigns.com/rd/entry/database_profiles_in_appfuse_2). > Matt suggested that comments (questions) be posted here... > > Looking at my pom.xml I can see that properties for each database type > are placed within separate profiles. But that differs for the default, > MySql database properties, which are placed within a <properties/> > element. Why is that? Shouldn't those MySql properties be placed in a > <profile/> element of their own, which then includes an <activation/> > element in order to set them as the default database properties?
Yes, it makes sense to put them in a profile. I've thought about this in the past and haven't changed it. I'm not sure if I had a good reason or not. > > I'm asking these questions because I'd like to change the default > database for my applications - preferably to use an embedded Derby > database. I would try it and see how it works. Matt > > Thanks, > > Paul. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
