Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/UserGuide/MOXy/Simple Values/Special Schema Types/Binary Types"
< EclipseLink | UserGuide | MOXy | Simple Values | Special Schema Types
Line 13: | Line 13: | ||
− | == byte [] versus Byte[] == | + | == byte[ ] versus Byte[] == |
Unlike other Java primitive/wrapper types, Eclipselink differentiates between '''byte[]''' (primitive) and '''Byte[]''' (wrapper) data types. By default, '''byte[]''' will marshal to a single "blob" of XML, whereas '''Byte[]''' will marshal each byte as its own element. | Unlike other Java primitive/wrapper types, Eclipselink differentiates between '''byte[]''' (primitive) and '''Byte[]''' (wrapper) data types. By default, '''byte[]''' will marshal to a single "blob" of XML, whereas '''Byte[]''' will marshal each byte as its own element. |
Revision as of 12:29, 28 June 2011
EclipseLink MOXy
EclipseLink | |
Website | |
Download | |
Community | |
Mailing List • Forums • IRC • mattermost | |
Issues | |
Open • Help Wanted • Bug Day | |
Contribute | |
Browse Source |
Key API
Contents
Binary Types
There are a few extra things to consider when mapping to fields of type byte[ ] or Byte[].
byte[ ] versus Byte[]
Unlike other Java primitive/wrapper types, Eclipselink differentiates between byte[] (primitive) and Byte[] (wrapper) data types. By default, byte[] will marshal to a single "blob" of XML, whereas Byte[] will marshal each byte as its own element.