Now I wonder if using crossdb for Torque would be a good idea. Reason being is that you wouldn't have to rebuild all your classes and scripts like you would using Torque now if you wanted to use a different database. Or even modifying the database, you wouldn't have to rebuild everything, just change it in one spot and run it. And when distributing it, the end user wouldn't need to run the builds again either, they could just package it in a war file or something, get the right crossdb implementation and run it.
Food for thought. Travis -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
