Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338130 - Empty element should unmarshal to null for BigInteger and BigDecimal properties
Summary: Empty element should unmarshal to null for BigInteger and BigDecimal properties
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: Blaise Doughan CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 331158
Blocks:
  Show dependency tree
 
Reported: 2011-02-24 13:01 EST by Blaise Doughan CLA
Modified: 2022-06-09 10:09 EDT (History)
1 user (show)

See Also:

Attachments
MOXy - Test Cases (969 bytes, patch)
2011-03-04 12:49 EST, Blaise Doughan CLA 		no flags Details | Diff
Core - Fix (1.09 KB, patch)
2011-03-04 12:51 EST, Blaise Doughan 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 Blaise Doughan CLA 2011-02-24 13:01:19 EST 
Although for numeric objects with a primitive counterpart empty elements unmarshal to the value 0.  For the following types and empty element should unmarshal as null:

  - BigInteger
  - BigDecimal
  - Boolean
Comment 1 Blaise Doughan CLA 2011-03-04 12:49:24 EST 
Created attachment 190420 [details]
MOXy - Test Cases
Comment 2 Blaise Doughan CLA 2011-03-04 12:51:06 EST 
Created attachment 190421 [details]
Core - Fix

Changes changed the following methods in XMLConversionManager to return null instead of 0:

- convertObjectToBigInteger
- convertObjectToBigDecimal
Comment 3 Blaise Doughan CLA 2011-03-04 13:19:01 EST 
Checked into trunk at rev:  9076

Code reviewed by:  Rick Barkhouse
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:09:27 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink