db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From suneel gupta <gofor_sun...@yahoo.co.in>
Subject UNABLE TO CONFIGURE TORQUE AS A STANDALONE
Date Fri, 02 Jan 2004 13:31:17 GMT
HELLO  EVERYBODY

I WANT  TO CONFIGURE TORQUE OUTSIDE TURBINE BUT IT
CREATES SOME PROBLEM.

FIRSTLY I HAVE DOWNLOAD THE   torque-3.1-src.tar  AND 
ALSO  JAR FILES  FROM THE  TORQUE SITES.

AFTER READING  TO HOW TO CONFIGURE TORQUE I HAVE  EDIT
 THE FOUR  FILES 
WHICH ARE  

1 =>
/home/satya/torque/src/generator/src/conf/build.properties
which contents  is

#
-------------------------------------------------------------------
#
# T O R Q U E  C O N F I G U R A T I O N  F I L E
#
#
-------------------------------------------------------------------
# This file contains the most commonly used
properties. For a
# a complete list of build properties, please refer
to:
#  
http://jakarta.apache.org/turbine/torque/properties-reference.xml
#
-------------------------------------------------------------------


#
-------------------------------------------------------------------
#
#  P R O J E C T
#
#
-------------------------------------------------------------------
# This is the name of your Torque project. Your
non-Java generated 
# files will be named using the project name selected
below. If your
# project=killerapp then you will have a generated:
#
#   killerapp-schema.sql
#
# The custom is then to also rename your project XML
schema from
# project-schema.xml to killerapp-schema.xml. This is
required 
# for a few targets such as datasql, datadump, and
datadtd.
#
-------------------------------------------------------------------

torque.project = killerapp


#
-------------------------------------------------------------------
#
#  T A R G E T  D A T A B A S E
#
#
-------------------------------------------------------------------
# This is the target database, only considered when
generating
# the SQL for your Torque project. Your possible
choices are:
#
#   axion, cloudscape, db2, db2400, hypersonic,
interbase, mssql,
#   mysql, oracle, postgresql, sapdb, sybase
#
-------------------------------------------------------------------

torque.database = mysql


#
-------------------------------------------------------------------
#
#  O B J E C T  M O D E L  I N F O R M A T I O N
#
#
-------------------------------------------------------------------
# These settings will allow you to customize the way
your
# Peer-based object model is created.
#
-------------------------------------------------------------------
# addGetByNameMethod
#   If true, Torque adds methods to get database
fields by name/position.
#
# addIntakeRetrievable
#   If true, the data objects will implement Intake's
Retrievable 
#   interface
#
# addSaveMethod
#   If true, Torque adds tracking code to determine
how to save objects.
#
# addTimeStamp
#   If true, Torque true puts time stamps in generated
om files.
#
# basePrefix
#   A string to pre-pend to the file names of base
data and peer objects.
#
# complexObjectModel
#   If true, Torque generates data objects with
collection support and 
#   methods to easily retreive foreign key
relationships.
#
# targetPackage
#   Sets the Java package the om files will generated
to, e.g. 
#   "com.company.project.om".
#
# useClasspath
#   If true, Torque will not look in the
<code>templatePath</code> directory,
#   for templates, but instead load them from the
classpath, allowing you to 
#   use Torque without extracted it from the jar.
#
# useManagers
#   If true, Torque will generate Manager classes that
use JCS for caching.
#   Still considered experimental.
#
-------------------------------------------------------------------

torque.targetPackage = org.iitk.killerapp.om

torque.addGetByNameMethod = true
torque.addIntakeRetrievable = false
torque.addSaveMethod = true
torque.addTimeStamp = true
torque.basePrefix = Base
torque.complexObjectModel = true
torque.useClasspath = false
torque.useManagers = false


#
-------------------------------------------------------------------
#
#  D A T A B A S E  S E T T I N G S
#
#
-------------------------------------------------------------------
# JDBC connection settings. This is used by the
JDBCToXML task that
# will create an XML database schema from JDBC
metadata. These
# settings are also used by the SQL Ant task to
initialize your
# Torque system with the generated SQL.
#
# sameJavaName
#   If true, the JDBC task will set the javaName
attribute for the tables 
#   and columns to be the same as SQL name.
#
-------------------------------------------------------------------

#torque.database.createUrl =
jdbc:postgresql://127.0.0.1:5432/template1
#torque.database.buildUrl =
jdbc:postgresql://127.0.0.1:5432/bookstore
torque.database.url = jdbc:mysql://127.0.0.1/killerapp
torque.database.driver = org.gjt.mm.mysql.Driver
torque.database.user = apdas
torque.database.password = apdasetslab
torque.database.host = 127.0.0.1

torque.sameJavaName = false


2 => under the schema directory 

there are two files which are 

1:=>/home/satya/torque/src/generator/src/schema/killerapp-schema.xml
which content is

<database name="killerapp"
                         defaultIdMethod="idbroker"> 

              <table name="ID_TABLE">
                <column name="ID_TABLE_ID"
required="true" primaryKey="true" type="INTEGER"/>
                <column name="TABLE_NAME"
required="true" size="255" type="VARCHAR"/>
                <column name="NEXT_ID"
type="INTEGER"/>
                <column name="QUANTITY"
type="INTEGER"/>

                <unique>
                  <unique-column name="TABLE_NAME"/>
                </unique>

              </table>

              <table name="TURBINE_PERMISSION"
idMethod="idbroker">
                <column name="PERMISSION_ID"
required="true" primaryKey="true" type="INTEGER"/>
                <column name="PERMISSION_NAME"
required="true" size="99" type="VARCHAR"
javaName="Name"/>

                <unique>
                  <unique-column
name="PERMISSION_NAME"/>
                </unique>

              </table>

              <table name="TURBINE_ROLE_PERMISSION">
                <column name="ROLE_ID" required="true"
primaryKey="true" type="INTEGER"/>
                <column name="PERMISSION_ID"
required="true" primaryKey="true" type="INTEGER"/>

                <foreign-key
foreignTable="TURBINE_ROLE">
                  <reference local="ROLE_ID"
foreign="ROLE_ID"/>
                </foreign-key>

                <foreign-key
foreignTable="TURBINE_PERMISSION">
                  <reference local="PERMISSION_ID"
foreign="PERMISSION_ID"/>
                </foreign-key>
              </table>

            </database>

2=> files under the schema directory  which is
/home/satya/src/generator/src/conf/id-table-schema.xml
 which content is

?xml version="1.0" encoding="ISO-8859-1"
standalone="no"?>
<!DOCTYPE database SYSTEM
"http://db.apache.org/torque/dtd/database_3_1.dtd">

<!--
====================================================================
-->
<!--                                                  
                   -->
<!-- I D  B R O K E R  S C H E M A                    
                   -->
<!--                                                  
                   -->
<!--
====================================================================
-->
<!-- This is the XML schema use by Torque to generate
the SQL for         -->
<!-- ID_TABLE table used by the id broker mechanism in
Torque.            -->
<!--
====================================================================
-->
<!-- @author: <a
href="mailto:jvanzyl@apache.org">Jason van Zyl</a>    
  -->
<!-- @version $Id: id-table-schema.xml,v 1.2
2003/07/24 12:40:41 mpoeschl Exp $ -->
<!--
====================================================================
-->

<database name="killerapp">
  <table name="ID_TABLE" idMethod="idbroker">
    <column name="ID_TABLE_ID" required="true"
primaryKey="true" type="INTEGER"/>
    <column name="TABLE_NAME" required="true"
size="255" type="VARCHAR"/>
    <column name="NEXT_ID" type="INTEGER"/>
    <column name="QUANTITY" type="INTEGER"/>

    <unique>
      <unique-column name="TABLE_NAME"/>
    </unique>

  </table>
</database>


now  after  created the  Torque.properties  

i want to invoke Torque  to create  peer classes  or 
for object-modelling


but  when  i have  want  to compile  build-torque.xml
where  it is  located using ant tools
then it shows

[satya@ETS01 conf]$ ant -f build-torque.xml
Buildfile: build-torque.xml

BUILD FAILED
/home/satya/torque/src/generator/src/conf/build-torque.xml:67:
taskdef A class needed by class
org.apache.torque.task.TorqueDataModelTask cannot be
found: org/apache/tools/ant/Task

Total time: 7 seconds
[satya@ETS01 conf]$

so please anybody help me  and try to solve my problem

or if anyone knows fully configuration of Torque as a
Standalone  in Linux then please write me step by step


from
suneel gupta








________________________________________________________________________
Yahoo! India Mobile: Download the latest polyphonic ringtones.
Go to http://in.mobile.yahoo.com

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


Mime
View raw message