Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362679 - Allow nillable option on TypeMappingInfo
Summary: Allow nillable option on TypeMappingInfo
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-02 10:30 EDT by Denise Smith CLA
Modified: 2022-06-09 10:35 EDT (History)
1 user (show)

See Also:

Attachments
Proposed changes and tests (14.42 KB, patch)
2011-11-02 12:15 EDT, Denise Smith 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 Denise Smith CLA 2011-11-02 10:30:06 EDT 
Add an option on TypeMappingInfo to allow global elements to be generated as nillable.
Comment 1 Denise Smith CLA 2011-11-02 12:15:16 EDT 
Created attachment 206345 [details]
Proposed changes and tests
Comment 2 Denise Smith CLA 2011-11-03 10:48:07 EDT 
TypeMappingInfo has a nillable option and if this is set the corresponding global element (if one exists) in the schema will be marked as nillable.
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:16:40 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:35:01 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink