-
Notifications
You must be signed in to change notification settings - Fork 7
Entity Properties
01es edited this page Aug 28, 2024
·
4 revisions
Composite key -- property key
with type DynamicEntityKey
.
Its nature is that of a calculated property. Its string representation is a concatenation of values for all key member properties, separated by the specified separator (
by default).
Property P
declared by entity E
represents a one-to-one association if:
-
P
is of an entity typePE
. -
PE
has key typeK
andK <= E
(in terms of subtyping) and (K
is persistent or synthetic-based-on-persistent).
Example:
class Vehicle extends AbstractPersistentEntity<String> {
// one-to-one association
@IsProperty VehicleDetails details;
}
class VehicleDetails extends AbstractPersistentEntity<Vehicle> {
@IsProperty Vehicle key;
}
Such properties are implicitly calculated.
In the example above, the value of Vehicle.details
for any given Vehicle
v
will be calculated
to find the VehicleDetails
associated with v
, if such an association indeed exists.
Per aspera ad astra
- Web UI Design and Web API
- Safe Communication and User Authentication
- Gitworkflow
- JavaScript: Testing with Maven
- Java Application Profiling
-
TG Development Guidelines
- TLS and HAProxy for development
- TG Development Checklist
- Entities and their validation
- Entity Properties
- Entity Type Enhancement
- EQL
- Tooltip How To
- All about Matchers
- Streaming data
- Synthetic entities
- Activatable entities
- Jasper Reports
- Opening Compound Master from another Compound Master
- Window management test plan
- Multi Time Zone Environment
- GraphQL Web API
- Guice
- Maven
- Full Text Search
- Deployment recipes
- Application Configuration
- JRebel Installation and Integration
- Compile-time mechanisms