Entity Implementation Specifics

The Entity Implementation Specific details for the artifact can be specified from the Details tab in the Tigerstripe Entity editor. The following information is available in the Details tab:

Interface Package: the interface package where the corresponding Java interface is generated. This option only applies to the J2EE Integration Profile.
Extensibility: the extensibility parameter is a hint on how to go about generation for all three integration profiles. The available options are the following:
- Multi-Extendable:
- Single-Extendable:
- Non-Extendable:
Primary Key Type: Tigerstripe generates a Java Interface to represent the entity key. This key relies on a primary key field, for which the type must be specfied. By default, String is used, and mapped accordingly for the XML/WSDL generation.
Method Details: operations defined on Entity artifacts are mapped to methods on the facade that manages them. For each operation (include CRUD operations such as Create, Get, Set and Remove), you can select the following method profiles for generation by Tigerstripe.
- Simple: the operation in simple form (ie. directly as defined on the managed entity type)
- Bulk-Atomic: a bulk-atomic version of the operation, where the operation is applied to multiple instances of the managed entity type at once. The operation is atomic, that is, it either succeeds on all instances or fails on all instances.
- Bulk-Best-Effort: a bulk best-effort version of the operation, where it is applied to multiple instances of the managed entity type at once. This is a best effort operation, and it will return a list containing on which entity instance the operation failed.
- By-Template: a bulk-atomic operation that is applied on an entity instance that matches the provided template. Attribute matching is used to determine what instance of the managed entity type this operation shall be applied to. The operation is atomic, that is, it either succeeds on all selected instances or fails on all instances.
- By-Templates: a variation of the By-template operation where multiple templates are provided for attribute matching with instances. The list of instances is determined by matching all of the given templates.
- By-Template-Best-Effort: a best-effort version of the By-template operation.

Entity Implementation Specifics

Related Topics