-
Bug
-
Resolution: Done
-
Medium
-
Istanbul Release
-
None
There are several issues in the existing enitity classes in policy-models.
Most of these issues are in tables that are not really used (or populated with data), and eclipselink is not strict at all and thus not complaining about them.
For e.g.: In the table, jpatoscapolicyType_properties, the PROPERTIES (containing JpaToscaProperty) is a blob field specified using @ElementCollection. But JpaToscaProperty class is again annotated with @Entity which is not needed, the toscaproperty table will always be empty and the data is stored as a blob in jpatoscapolicyType_properties
Similar issues that are not caught by eclipselink exist in other places too.
As part of this JIRA, the issues identified will be presented to the team, and fixed.
Changes expected with the bug fix:
1) Fixes in some of JpaXXX classes where issues exist.
2) Corresponding changes in the db migrator script.
Note: Hopefully, no changes are expected to any tables that are actually used today