Community
Participate
Working Groups
In preparation for supporting package annotations in bug 265087 I am going to refactor the o.e.jpt.core.utility.jdt.Member hierarchy to add an AnnotatedElement interface. Provisional API changes: 1. Member will extend AnnotatedElement 2. All methods from Member will move to AnnotatedElement except isPersistable(CompilationUnit) and matches(String, int) 3. o.e.jpt.core.resource.java.JavaResourcePersistentMember will now extend the new JavaResourceAnnotatedElement. 4. These methods stay on JavaResourcePersistentMember, all others move up to JavaResourceAnnotatedElement: setPrimaryAnnotation(String, Iterable<String>); boolean isPersistable(); boolean isFinal(); boolean isFor(String memberName, int occurrence); void resolveTypes(CompilationUnit astRoot); 5. o.e.jpt.core.resource.java.AnnotationDefinition method signatures become: Annotation buildAnnotation(JavaResourceAnnotatedElement,AnnotatedElement); Annotation buildAnnotation(JavaResourceAnnotatedElement, IAnnotation); Annotation buildNullAnnotation(JavaResourceAnnotatedElement parent); 6. JavaGeneratorContainer initialize and update methods take a JavaResourceAnnotatedElement. Making this change since some JPA extensions have generators that are allowed on packages, don't want to limit to Members. 7. JavaQueryContainer initialize and update methods take a JavaResourceAnnotatedElement.
Created attachment 180709 [details] proposed patch against head
fixed in 3.0M3
This refactoring has been verified