Define a class across XML, SQL, and Java.
Attribute | Description | Required |
name | the fully-qualified name of the class (in Java). | Yes |
identity | field-name for primary key in database | Yes if a database class ('-factories' is turned on) |
extends | a java class to extend - must be a class specified in a map-file (or org.ephman.abra.utils.Versioned | Identified). | No |
implements | a comma seperated list of fully-qualified Java classes to implement. | No |
descendant | a hand-written class that will extend this one - tells the generated factory to create the instances of 'descendant' using the generic constructor. | No |
end-date | boolean specifying if end-dateing should be used instead of deleting (Column END_DATE will be added and given a timestamp on delete instead of deleting row). | No (Database-only) |
cache-type | if set to 'persistent' keep objects cached-indefinitely (Identfied) these are static-data classes; otherwise extend Versioned and do in transaction cache only. | No (will default to 'transacted' and become a Versioned object) |
abstract | boolean to make this class abstract. | No |
many-to-many | boolean to make this class define a many-to-many relationship. Special case where exactly 2 nested field expected each a database class in the map-file. | No |
the map-to node specifies table-names and xml-node names for mapping
the class-view node allows description of data abstractions where mapping/translation can be generated. The <view> tag is used on a field-by-field basis to specify which fields belong in a view. A class may have multiple class-views.
The constraint node describes an sql constraint which exists on a set of fields.
The repeating field node describes a field.
Copyright © 2000,2001,2002 Paul Bethe and Richie Bielak. All rights Reserved.