Hm...normally in the use of Torque, you have a naturally have a project-schema.xml. I imagine the jdbc target generates to just schema.xml as you wouldn't want it to overwrite your hand-created schema.xml.
My guess is that since you'll probably only run the jdbc target once to create the schema.xml and then hand-edit it for the rest of the project (is there a reason you'll keep running the jdbc target), so renaming it the first time to project-schema.xml shouldn't be a big deal. I'm new to Torque development, but it looks like the jdbc task has not been kept up to date on the format of the *-schema.xml. For now you'll have to hack the jdbc output into the currently-accepted Torque DTD. It shouldn't be too bad. - Stephen > -----Original Message----- > From: Thomas Wheeler [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, July 23, 2002 2:19 PM > To: 'Turbine Torque Users List' > Subject: RE: templatePath > > Thanks for the patch, I'll put that into my build. > > Now I'm stuck again. <aside type="rant">I'm not laying blame or passing > judgment since I'm using a beta, but gosh it's frustrating using a product > with outdated documentation!</aside> > > Anyway. I've used the jdbc target to create a src/schema.xml from my > existing database metadata. And I'm able to generate an SQL schema from it > (src/sql/* files). Now I want to generate the om target. This expects to > work from a schema/*-schema.xml. Okay, fine. So the question is, how do I > generate a schema/*-schema.xml from my src/schema.xml? There doesn't appear > to be a target that does this, and the extremely-naive approach of copying > src/schema.xml to schema/myproject-schema.xml blows up. Help...? > > -Thomas > > -----Original Message----- > From: Stephen Haberman [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, July 23, 2002 11:38 AM > To: 'Turbine Torque Users List' > Subject: RE: templatePath > > > Hm...good job of tracking that down. > > I've got a patch into velocity-dev that will let us get around this > thorny template/useClasspath issue but until then, I'll submit a patch > to handle this. > > Actually, now that I look, I've got a larger patch for build-torque.xml > that fixes this issue. I'm waiting for commit access to put it in the > repository, but if you want, the approach I take in the patch is: > > Use ant's condition task like: > > <target name="check-use-classpath"> > <condition property="torque.internal.useClasspath"> > <equals arg1="${useClasspath}" arg2="true"/> > </condition> > </target> > > Then change the target sql-template/sql-classpath targets by adding a > dependents="check-use-classpath" and change the if/unless from just > useClasspath to torque.internal.useClasspath which will only be set > ifuseClasspath is true. > > - Stephen > > > -----Original Message----- > > From: Thomas Wheeler [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, July 23, 2002 11:29 AM > > To: 'Turbine Torque Users List' > > Subject: RE: templatePath > > > > Solution found. Developers, I hope you're listening. (msegalla, I > hope > > you're listening too :).) > > > > The "sql-classpath" target was being built instead of "sql-template". > > Apparently, if sql-template is to be built, the useClassPath property > must > > be undefined (not just set to false) -- otherwise it will use the > > sql-classpath target. > > > > According to the Ant documentation, using "if" in a <target> executes > the > > target if the property is set, regardless of the value it is set to. > So the > > target > > > > <target name="sql-classpath" if="useClasspath"> > > > > executes if useClasspath is set _at all_. A brief scan of the docs > doesn't > > describe this behavior. > > > > -Thomas > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:turbine-torque-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:turbine-torque-user- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
