One additional thought here. There is a Torque.init(Configuration) method that can be used instead of Torque.init(fileName). You could build your own commons Configuration object from Turbine's properties to match your needs.
> -----Original Message----- > From: Helge Weissig [mailto:[EMAIL PROTECTED] > > The requirement to have the name in the schema and in the > configuration match is somewhat cumbersome for a multi-developer > environment, where each developer needs to have their own database. > The old way (way old!!) used to be that the db name was only > specified once in TurbineResources.properties and hence needed to be > changed only once when setting up a new sandbox. Maybe it's easier > when using the Turbine M.E.T.A approach... does anyone know? > > As for using the Peers in the oracle db, we don't have any. The > database is a commercial one and we only use very few tables > from it. > Since learning about the jdbc2xml capabilities of Torque, I have > considered generating the peers for those. > Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
