The following table shows the mapping of class stereotypes to attribute stereotypes.
Table 1. Mapping of Class and Attribute StereotypesClass Stereotype
|
Valid Attribute Stereotypes
|
audit_mappings |
audit_mappings |
domain_definition |
N/A |
entity |
details, key |
facade |
N/A |
listrdo |
dataitem |
loader |
N/A |
process |
N/A |
rdo |
dataitem |
struct |
default |
webservice |
N/A |
wsinbound |
N/A |
- Attribute names must be unique within a class.
- Attributes must be defined in terms of domain definitions.
- Since attributes ultimately appear in generated Java code, their names must be valid Java identifiers.
- The order of attributes in the primary key of an entity is determined by the order in which the attributes appear in the entity class. Since their order in the entity is not critical, you can change this order to obtain the primary key configuration you desire.