Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348756 - m_cascadeOnDelete boolean should be changed to Boolean
Summary: m_cascadeOnDelete boolean should be changed to Boolean
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: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-08 10:37 EDT by Guy Pelletier CLA
Modified: 2022-06-09 10:31 EDT (History)
1 user (show)

See Also:


Attachments
Proposed changes (58.58 KB, patch)
2011-07-04 11:39 EDT, Guy Pelletier CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Guy Pelletier CLA 2011-06-08 10:37:12 EDT
m_cascadeOnDelete variable from EntityAccessor should be changed to a Boolean from boolean. As a primitive, it always has a value and is therefore always written out to XML. It should only be written out when explicitly set.

This was witnessed when working through a extensible/metadata repository example with Doug.
Comment 1 Guy Pelletier CLA 2011-07-04 11:39:24 EDT
Created attachment 199058 [details]
Proposed changes
Comment 2 Guy Pelletier CLA 2011-07-04 11:41:21 EDT
The attached patch corrects all empty type mappings (keeps them all the same). Also, current metadata model format if used to write an XML file would always write out boolean elements even though you called its respective set method with false.
Comment 3 Guy Pelletier CLA 2011-07-04 14:00:28 EDT
Changes have been submitted.

Verified by: Tom Ware

Tests: Test (testXMLEntityMappingsWriteOut) added to EntityMappingsAdvancedJUnitTestCase
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:31:15 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink