Community
Participate
Working Groups
Created attachment 236634 [details] JUnit Test case for MOXy marshalling bug when target object is derived from Collection If the target object to be marshalled ultimately is derived from a collection MOXy's behavior is different from the JAXB reference implementation. The attached JUnit test has the following object hierachy: ItemManager -extends-> MyMoxyManager MyMoxyManager -extends-> MoxyManagerImpl MoxyManagerImpl -implements-> MoxyManager MoxyManager -extends-> MoxyList MoxyList -extends-> Collection The expected resulting XML is: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <itemManager> <items> <value>2</value> </items> </itemManager> but MOXy JAXB marshalls to an empty string. This seems to be a bug. see http://stackoverflow.com/questions/19347743/why-does-moxy-jaxb-marshal-to-empty-string-while-jaxb-reference-implementation-d and the attached JUnit test.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink