Ticket #206 (closed enhancement: fixed)

Opened 4 years ago

Last modified 4 years ago

Support multiple aspect bindings per team

Reported by: stephan Owned by: stephan
Priority: major Milestone: OTDT_1.2.7
Component: otequinox Version: 1.2.6
Keywords: Cc:

Description

In order to help reduce code scattering when using OT/Euqinox it should be officially supported to define multiple aspectBindings for the same team class. Thereby, roles of this team can adapt base classes from different bundles - the team acts as a coherent view on all relevant base classes, no matter their dwellings.

Generally OT/Equinox already copes with such situation. However, team instantiation and activation needs to be specified more precisely for such cases.

Change History

Changed 4 years ago by stephan

  • status changed from new to closed
  • resolution set to fixed

Implemented as part of r19670:

  • Only instantiate each team class once
  • Report (at runtime) conflicting activation requests from different aspect bindings

Application of this feature can now be found at team class org.objectteams.otdt.pde.validation.BundleValidation.

Note: See TracTickets for help on using tickets.