Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
From: "Cameron Hickey" <cam@panoramatos.com>
To: "'Apache Torque Users List'" <torque-user@db.apache.org>
Subject: Generated OM classes have $clo instead of column names
Date: Thu, 27 May 2004 17:14:10 +0300
Message-ID: <002101c443f4$e3f5bb30$0100a8c0@CameronAcer>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <001d01c443b7$b1050970$690ba8c0@int.globaltechbg.com>

I have been using torque 3.0 for the last year, and now that I am
starting a new project I decided to upgrade to the 3.1 split generation
tool.

After managing to get the JDBC task to properly generate a new schema
file from an existing database I need to use, I tried using the main ant
task to generate the OM classes.  Everything actually worked until I
compiled the project and discovered that the Base classes all had "$clo"
everywhere the column names should be.

This is an example:

    /** The value for the $clo field */
    private String $clo;
      

I assume that this is caused by some portion of the velocity processing
not properly replacing this field ($clo) with the value from the XML
schema, but I cannot understand why.

I thought it might be because I was using a schema generated by the JDBC
task, but then I imported a schema I know works fine in torque 3.0 and
the same thing happened.

I don't know a lot about velocity, or have any idea how to debug it, but
I hope there is something I can change in my build.properties file to
make it properly recognize and use the column names from the XML file.

Any ideas?

Cameron


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org