Annotations: Only instantiate annotations by migrator if needed
* Refactor the AnnotationValueService to add a check for the need to instantiate annotations to the public API. The performance impact is neglible due to caching support in the service at two relevant places. * Use the provided method to check if a "migration" for adding annotations is actually needed. This avoids indicating the need for migration for every model as in the previous implementation. Issue-Ref: 3838 Issue-Url: https://af3-developer.fortiss.org/issues/3838 Signed-off-by:Alexander Diewald <diewald@fortiss.org>
Showing
- org.fortiss.tooling.base/src/org/fortiss/tooling/base/annotation/.ratings 2 additions, 2 deletions...ing.base/src/org/fortiss/tooling/base/annotation/.ratings
- org.fortiss.tooling.base/src/org/fortiss/tooling/base/annotation/AnnotationValueService.java 30 additions, 32 deletions...rtiss/tooling/base/annotation/AnnotationValueService.java
- org.fortiss.tooling.base/src/org/fortiss/tooling/base/annotation/IAnnotationValueService.java 8 additions, 0 deletions...tiss/tooling/base/annotation/IAnnotationValueService.java
- org.fortiss.tooling.base/src/org/fortiss/tooling/base/migration/.ratings 1 addition, 1 deletion...ling.base/src/org/fortiss/tooling/base/migration/.ratings
- org.fortiss.tooling.base/src/org/fortiss/tooling/base/migration/AddMissingAnnotationsMigrationProvider.java 16 additions, 1 deletion...ase/migration/AddMissingAnnotationsMigrationProvider.java
- org.fortiss.tooling.base/src/org/fortiss/tooling/base/utils/.ratings 1 addition, 3 deletions....tooling.base/src/org/fortiss/tooling/base/utils/.ratings
- org.fortiss.tooling.base/src/org/fortiss/tooling/base/utils/AnnotationUtils.java 7 additions, 0 deletions...e/src/org/fortiss/tooling/base/utils/AnnotationUtils.java
Loading
Please register or sign in to comment