Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331586 - Additional Optional JAXB test failures
Summary: Additional Optional JAXB test failures
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Matt MacIvor CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-01 14:03 EST by Matt MacIvor CLA
Modified: 2022-06-09 10:08 EDT (History)
0 users

See Also:

Attachments
Proposed Fix (6.98 KB, patch)
2010-12-01 16:03 EST, Matt MacIvor CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matt MacIvor CLA 2010-12-01 14:03:05 EST 
Several issues with EclipseLink JAXB have been uncovered by the optional validation tests since the implementation of the validation feature.

-If a nillable element is required, it's MarshalNullRepresentation should be set to XSI_NIL

-If an anonymous complex type has inheritance, no InheritancePolicy should be setup since there's no class indicator value available. Instead, mappings from superclass should be generated directly on the subclass.

-When writing an attribute to a ContentHandlerRecord, if the attribute represents a namespace declaration, startPrefixMapping should be called on the nested ContentHandler.
Comment 1 Matt MacIvor CLA 2010-12-01 16:03:55 EST 
Created attachment 184303 [details]
Proposed Fix
Comment 2 Matt MacIvor CLA 2010-12-01 16:05:27 EST 
atttached patch checked in to SVN
Reviewed by Blaise Doughan
Comment 3 Matt MacIvor CLA 2010-12-06 16:13:28 EST 
closing as fixed
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:08:33 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink