Hi,
There are a couple of files in a new conf/torque directory
that need to be eyeballed.
There are two XML schemas, one for the base turbine system,
and one for the table needed by the id broker. Also, temporarily,
present is the SQL file generated by Torque.
I would like to use these XML schemas to generate everything
needed for a turbine installation. I just want to make sure
everything is cool before letting the TDK with Torque integrated.
When we fix anything that needs to be fixed in the XML
schemas I'd like to:
1. Get rid of all the OMGen* files in the org.apache.turbine.tools
package because Torque deals with it all now.
2. Move all the Torque config files to the new conf/torque
directory and use the conf generator to manage the inclusion
of Torque config files in the TDK.
3. Add a build target that would package up Torque by itself
in a JAR file so it can be used by people who don't
use the TDK. It would package up the necessary Torque
classes, Ant, Xerces, the torque config files, and some build
scripts so that Torque can be easily used with Turbine
without the TDK.
It would also be nice to come up with a standard way to
use Torque. I was thinking there would be:
1. turbine-schema.xml (base turbine system)
2. id-table-schema.xml (id broker table)
3. project.xml (project specific tables)
And have targets to initialize the system (1. & 2.) and
a target for regenerating 3. Could probably use the
sql Ant task for taking care of these things fairly
cleanly. Any thoughts?
I'd like to get a standard setup so I can use this
in the TDK.
Thanks,
jvz.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
