| ILOG JRules User Guide > Customizing JRules > Tasks > Customizing Rule Team Server > Using Specific Rule Model Annotations |
Using Specific Rule Model Annotations |
PREVIOUS NEXT |
You can customize the rule model extension files (.brmx and .brdx) directly in the XML files, or in the Rule Studio Rule Model Extension Editor. You can provide annotations that are specific to Rule Team Server in these extension files.
Table 1 describes these Rule Team Server specific annotations and their purposes.
Annotation Tag |
Description |
|---|---|
column-length |
The length of the column to create in the database to store this feature. |
clob |
Whether or not you should use a CLOB column to store the attribute.
It can be true or false. |
columnName |
The name of the column in the database.
For instance, if the name of the attribute is also an SQL keyword, it cannot be used as a column name. Therefore you can use this annotation to specify a different name. |
renderer-type |
To specify your own renderer type (see Implementing a Custom Property Editor for Rule Team Server). |
validator-class |
The fully qualified name of your own validator (see Defining a Custom Type Validator). |
foreignkey-name |
The name of the foreign key.
For instance, when an attribute is an enumeration or a hierarchy, there is a foreign key created in the database between the attribute database column and the database table that contains the values for this hierarchy or enumeration.
The name of this foreign key is generated automatically. However, if there are two attributes of the same enumeration or hierarchy in the class, the same foreign key name is generated for both attributes so the script cannot be executed. Consequently, this annotation should be used in order to specify different names. |
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |