Hi,
has the subclasses concept change from the old (encoupled) torque to the
new one. Because if I try to build a OM with the new Torque I'm getting
compiliation errors, every time i'm declaring a subclass of a existing
table, this happens becaus the return types of the subclass are not the
same as the ones of the superclass.
Could anybody tell me how the make something like this in torque 3.0 (with
the old version it worked) :
----------
<table name="RDF">
<column name="RDF_ID" required="true" autoIncrement="true"
primaryKey="true" type="INTEGER"/>
<column name="TITLE" size="255" type="VARCHAR"/>
<column name="BODY" size="255" type="VARCHAR"/>
<column name="URL" size="255" type="VARCHAR"/>
<column name="AUTHOR" size="255" type="VARCHAR"/>
<column name="DEPT" size="255" type="VARCHAR"/>
</table>
<table name="subRDF" baseClass="org.mycompany.newapp.om.Rdf">
<column name="RDF_ID" required="true" autoIncrement="true"
primaryKey="true" type="INTEGER"/>
<column name="ANYTHING" size="255" type="VARCHAR"/>
</table>
-----------
I figured out, that it works if I add an Alias="Rdf" but then I doesn't
create the defined columns in subrdf. either adding an base Peer doesn't help.
So how could this be done???
Thx and Greetings
Gandulf Kohlweiss
--
To unsubscribe, e-mail: <mailto:turbine-torque-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-torque-user-help@;jakarta.apache.org>
