Community
Participate
Working Groups
Build Identifier: 2.3.0-SNAPSHOT (20110202.060516-27) If the class Foo with an abstract superclass is marshalled, the output looks like: <Foo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="foo"></Foo> instead of <Foo></Foo> It causes another problems when you try to unmarshal such string. If there is any such class in JAXBContext, every other class marshalled with the marshaller (created from such context) has similar redundant attributes. Reinitializating JAXBContext doesn't help. Reproducible: Always Steps to Reproduce: See the attached test cases.
Created attachment 188162 [details] Test Cases FooTest - how it should work FooWithAncestor - how it doesn't work
Fixed related bug 340671 which covered this use case as well.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink