Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C40B68.2ED9B5DA"
Subject: [DB Torque Wiki] Updated:  FrontPage
Date: Tue, 16 Mar 2004 16:05:56 +0100
Message-ID: 
 <3418F3471F1CA4409901547349FFAE2E011D0447@ftrdmel2.rd.francetelecom.fr>
Thread-Topic: [DB Torque Wiki] Updated:  FrontPage
Thread-Index: AcQLaC0+fZPK10mnRCyYIfwsm6BJqg==
From: "zze-joigneur DODGE N ext FTRD/SVA/GRE"
 <ndodge.ext@rd.francetelecom.com>
To: <torque-dev@db.apache.org>

------_=_NextPart_001_01C40B68.2ED9B5DA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

I just wanted to share with you my solution to getting Torque 3.1 to
work.


First, I merged the Torque Gen 3.1 with Torque, so that all the files
needed were in one place.
After installing all the required libs, (by expanding the jars into a
common folder that was in the classpath), I kept getting an error:

ResourceManager : unable to find resource 'sql/base/Control.vm' in any
resource loader

After searching the web for a solution, I had a closer look into
build.properties, where I set=20

torque.useClasspath =3D true

That solved it.

Note: I lost some time by resolving all libs that weren't found when
using ant -debug. Turns out this is not necessary!


------_=_NextPart_001_01C40B68.2ED9B5DA--