| Summary: | AnnotationsProcessor should ignore synthetic methods | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Denise Smith <denise.mahar> | ||||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | ||||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Denise Smith
If these synthetic methods are not ignored running the JAXB tests (for example org.eclipse.persistence.testing.jaxb.typemappinginfo.MapStringIntegerTestCase ) will fail in jdk 1.7.0_02 as the cls.getDeclaredMethods returns the methods in a different order the synthetic methods will be found first and errors will occur such as marshalling the "item" element on our generatedWrapper class when it is marked transient. Created attachment 209279 [details]
2.3 proposed changes
Created attachment 209280 [details]
proposed trunk patch
Fix checked in to 2.3.3 and 2.4 The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |