Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332555 - setAttachmentMarshaller on JAXBMarshaller doesn't handle null
Summary: setAttachmentMarshaller on JAXBMarshaller doesn't handle null
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: Matt MacIvor CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-14 13:25 EST by Matt MacIvor CLA
Modified: 2022-06-09 10:03 EDT (History)
0 users

See Also:

Attachments
Proposed Fix (2.47 KB, patch)
2010-12-14 15:03 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 2010-12-14 13:25:52 EST 
When setAttachmentMarshaller on JAXBMarshaller is called with a null parameter, the attachment marshaller on the corresponding XMLMarshaller should be nulled out. Currently an AttachmentMarshallerAdapater is created with a null attachment marshaller and is set on the nested XMLMarshaller. This will cause NullPointerExceptions.

This also applies to setAttachmentUnmarshaller on JAXBUnmarshaller.
Comment 1 Matt MacIvor CLA 2010-12-14 15:03:19 EST 
Created attachment 185166 [details]
Proposed Fix
Comment 2 Matt MacIvor CLA 2010-12-14 16:19:57 EST 
Patch checked in to SVN
Reviewed by Blaise Doughan
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:03:07 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink