Packaging

Description

As a developer, I suggest to move the classes for representing schema information (ModelManager, EntityType, Attributes, and Relation) from the query package to a separate package because they are not only required for queries, but also for other purposes.

In addition, the distinction between "core" and "record" is not clear. Nor the reason, why two different containers are needed for generic condition. "Record" appears at first glance as the implementation detail of the query implementation; In this case, however, the class does not belong to the public API.

Furthermore, the classes "SearchService", "SearchQuery" and "Searchable" should be stored in a separate package, because they represent a separate function layer above the processing of structured queries.

In addition, the createQuery () method should be moved from the ModelManager interface to the BaseEntityManager interface (or better, its own QueryService), in order to be able to implement ModelManager as a pure repository of schema information.

Activity

Show:
Angelika Wittek
November 6, 2017, 12:44 PM
Angelika Wittek
November 27, 2017, 9:23 AM

See for a list of API changes

Assignee

Angelika Wittek

Reporter

Hans-Jörg Kremer

Labels

Process Step

Global

Eclipse Project

MDM Business Layer

Status

New

Components

None

User Story Name

Packaging

Implementer (Company)

None

Customer (Company)

None

Epic Link

Fix versions

Affects versions

Priority

Major
Configure