Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345666 - JAXB MARSHALS INVALID NULL URI PARAMETER TO SAX CONTENT HANDLER SRARTELEMENT()
Summary: JAXB MARSHALS INVALID NULL URI PARAMETER TO SAX CONTENT HANDLER SRARTELEMENT()
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-05-12 16:40 EDT by Blaise Doughan CLA
Modified: 2022-06-09 10:27 EDT (History)
1 user (show)

See Also:

Attachments
proposed fix and test case (7.42 KB, patch)
2011-05-13 12:25 EDT, 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 Blaise Doughan CLA 2011-05-12 16:40:06 EDT 
If we marshal an object with a member in the default namespace to a
SAXResult, Toplink JAXB supplies a null for the uri parameter of
ContentHandler.startElement().  This causes a crash when used with Sun's
XmlStreamBuffer SAXResult object.  While other SAXResult objects are more
lenient, according to the javadocs, null is not a valid value, and "" should
be passed in:
Comment 1 Matt MacIvor CLA 2011-05-13 12:25:14 EDT 
Created attachment 195605 [details]
proposed fix and test case
Comment 2 Matt MacIvor CLA 2011-05-13 13:57:03 EDT 
Attached patch checked in to SVN
Reviewed by Blaise Doughan
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:27:41 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink