Community
Participate
Working Groups
This seems depend on the 'combination' of types to create the jaxbContext. The java types we give to jaxb come from the methods on the SEI(service endpoint interface). I have a SEI with 3 methods, and this problem only happen in some combination of these 3 methods. Exception [EclipseLink-60] (Eclipse Persistence Services - 2.2.0.v20101012-r8345): org.eclipse.persistence.exceptions.DescriptorException Exception Description: The method [setValue] or [getValue] is not defined in the object [jaxb.dev.java.net.java.lang.ListOfString2]. Internal Exception: java.lang.NoSuchMethodException: jaxb.dev.java.net.java.lang.ListOfString2.getValue() Mapping: org.eclipse.persistence.oxm.mappings.XMLDirectMapping[value-->text()] Descriptor: XMLDescriptor(jaxb.dev.java.net.java.lang.ListOfString2 --> [DatabaseTable(ns0:sayHello)])
This bug is related to an issue in MappingsGenerator. A check is incorrectly determining that two separate TypeMappingInfo objects should map to the same complex type.
Created attachment 183803 [details] proposed fix and test case
Attached patch checked in to SVN Reviewed by David McCann
closing as fixed
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink