Community
Participate
Working Groups
There are currently 2 issues with List properties: 1. If a type is only referenced as the target of a many property then a NPE is thrown during JAXBContext initialization when bootstrapping from an XML schema. 2. If a type has multiple list properties then the reference descriptor for all mappings is set to the reference descriptor for the first many property.
Created attachment 172251 [details] MOXy - Test Cases
Created attachment 172252 [details] MOXy - Fix
Created attachment 172253 [details] Dynamic MOXy - Fix
Created attachment 172537 [details] Dynamic MOXy - Fix
Fix checked into trunk at rev: 7675 Fix checked into 2.1.1 at rev: 7674 1. In AnnotationsProcessor account for the fact that a classes super class may be null. This offered better performance than setting the super class to a wrapped version of Object which would then be ignored anyways. 2. When a class has multiple List properties List<Address>, List<Phone>, List<Address> and you ask XJC for the generic parameter for the first property you will get {Address}, for the second parameter you will get {Address, Phone}, and for the third property you will get {Address, Phone, Address}. Now the last parameter is assumed to be the type of the list instead of the first. Code reviewed by: Matt MacIvor
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink