Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335716 - JAXB: Byte[] and byte[] should not be treated the same.
Summary: JAXB: Byte[] and byte[] should not be treated the same.
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: 348116
  Show dependency tree
 
Reported: 2011-01-28 13:07 EST by Matt MacIvor CLA
Modified: 2022-06-09 10:35 EDT (History)
0 users

See Also:

Attachments
Proposed Fix and Tests (22.19 KB, patch)
2011-01-28 13:44 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 2011-01-28 13:07:23 EST 
In JAXB a property of type byte[] or a root level byte[] indicates binary data which is mapped to an element or attribute of type base64Binary. Currently EclipseLink treats Byte[] in the same way, mapping it to a base64Binary element and treating it as a possible attachment.

However Byte[] should be treated as a list of bytes, and be mapped like an Integer[] or any other primitive wrapper type. 

This discrepancy is causing failures in the JAX-WS TCK when run with EclipseLink as the JAXB provider.
Comment 1 Matt MacIvor CLA 2011-01-28 13:44:43 EST 
Created attachment 187863 [details]
Proposed Fix and Tests
Comment 2 Matt MacIvor CLA 2011-02-03 10:55:53 EST 
Attached patch checked in to SVN
Reviewed by Blaise Doughan
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:35:34 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink