Bug #4940
Refactor the overlapping DmoMeta, RecordMeta, and PropertyMeta classes into a more rational approach
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
History
#2 Updated by Ovidiu Maxiniuc over 3 years ago
The DmoMeta, RecordMeta, and PropertyMeta do overlap in some measure. They need to be refactored / simplified. Some work was done in 3821c/11655 when some attributes of PropertyMeta we delegated to new Property class (as opposed to copying them locally from Property annotation).
A secondary task here would be to eliminate all direct access to DMO annotations. They are very slow. They need to be read/processed a single time, when initializing the DMO and stored in other ORM structures. As result, the interfaces from com.goldencode.p2j.persist.annotation will not be imported/accessible in any of other classes than DmoMetadataManager, DmoMeta, and maybe a few similar ones.