If true, implementation classes are initialised implicitly in the constructor. If false, the initialiser must be invoked explicitly, after setting all fields. Generated factories take care of this protocol.

Applies to

▸ Model level: ☑ logical model ∙ ☑ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

If true, implementation classes are on-load-initialised in the on load constructor. If false, the initialiser must be invoked explicitly, under user control.

Applies to

▸ Model level: ☑ logical model ∙ ☑ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

If true, implementation classes are on-load-initialised in a special method annotated with JPA's PostLoad.

Applies to

▸ Model level: ☑ logical model ∙ ☑ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

If true, implementation classes are destroyed in the finalizer. If false, the destruction code (if existing) must be invoked explicitly.

Applies to

▸ Model level: ☑ logical model ∙ ☑ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

If specified, the evaluation of this condition indicates whether the structure of the underlying ADO class has changed fundamentally.

Such structure changes are in conflict with normal expectations of the behaviour of objects, they are used for technical reasons in some conditions.

Nevertheless, the interface shall be able to take this into account and must refresh (or reconstruct, reorganise etc.) all related views if such a change occurs.

Applies to

▸ Model level: ☑ logical model ∙ ☑ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states