Community
Participate
Working Groups
In the case where the user hands in a TypeMappingInfo for a given class, and there is also an ObjectFactory with a create method for that class, we should not add the duplicate entry to our classesToProcess array when processing the ObjectFactory. The code currently tries to guard against this with an List.contains() call, but this will not work for our JavaClass instances. XMLProcessor has a convenience method that handles this, (classExistsInArray) and should be made static such that it can be accessed from AnnotationsProcessor.
Created attachment 179051 [details] Contains proposed fix The List.contains() check is insufficient in this case. The existing convenience method on XmlProcessor is now used to guard against duplicate classes being added to the List of classes to process.
Created attachment 179126 [details] Contains proposed fix.
reviewed by: matt.macivor@oracle.com tests: all unit tests pass as expected
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink