Community
Participate
Working Groups
Currently XMLDescriptor is showing up as retaining the most memory (including transitive properties). Although this makes sense since this represents the stateful information, we should improve memory usage here where we can.
Created attachment 189988 [details] Core - Fix Changes: - Initialized size of primaryKeyFields from 2 to 1, ideally we would not initialize this collection all all since most XMLDescriptors do not have primary key fields, but this would be a larger change. - Use Collections.EMPTY_LIST & Collections.EMPTY_MAP for several list and map properties that are not used by OXM, but EclipseLink requires to be non-null. - Created a static variable for EMPTY_VECTOR where Collections.EMPTY_LIST can not be used. - Created a custom CopyPolicy that does nothing, since EclipseLink requires that a copy policy be set.
Created attachment 189992 [details] Core - Fix
Created attachment 190179 [details] Core - Fix Changes: - Initialized size of primaryKeyFields from 2 to 1, ideally we would not initialize this collection all all since most XMLDescriptors do not have primary key fields, but this would be a larger change. - Use Collections.EMPTY_LIST & Collections.EMPTY_MAP for several list and map properties that are not used by OXM, but EclipseLink requires to be non-null. - Created a static variable for EMPTY_VECTOR where Collections.EMPTY_LIST can not be used. Note: Due to an issue trying to have an optimized CopyPolicy with deployment XML, this change will not be covered by this bug.
Fix checked into trunk at rev: 9055 Fix checked into 2.2.1 at rev: 9056 Fix checked into 2.1.3 at rev: 9057 Code reviewed by: Rick Barkhouse
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
