How about a new DatabaseMapBuilder that enables you to connect db's to
Turbine more easily?
If my understanding is correct, currently you have one database map builder
class that you extend/customise to generate all your database maps.
If you want to remove or change a database you have to alter this class.
Would it not be a better idea to create individual mapbuilders for each
database you wish to link to Turbine, these could be specified in the
TurbineResouces.properties file. A 'manager' class could then generate the
dbmaps using these mapbuilders.
This enables Turbine Applications to be written as a discrete package that
can be added to an existing installation of Turbine, without any need for
recompilation of a mapbuilder class.
I think it is easier to specify databases this way, rather than hardcoding
it.
If you think this is a good idea, I'll send you the code.
If not, have I missed the point somewhere?
Andrew
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
