Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354257 - Issue with namespace declarations with XmlAnyElement
Summary: Issue with namespace declarations with XmlAnyElement
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: 2011-08-09 10:22 EDT by Matt MacIvor CLA
Modified: 2022-06-09 10:17 EDT (History)
0 users

See Also:

Attachments
Proposed fix and tests (13.87 KB, patch)
2011-08-09 15:01 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 Matt MacIvor CLA 2011-08-09 10:22:16 EDT 
When keeping a node as an org.w3c.dom.Element as part of an XmlAnyElement namespaces can be lost if the SAX parser doesn't have the namespacedeclarations feature set. 

This feature causes namespace declarations to be passed into the ContentHandler as Attributes. When this isn't set, the namespaces are only reported through the startPrefixMapping events. The startPrefixMapping events however, aren't called on the SAXFragmentBuilder for the root element of the fragment, so the namespace declarations are lost.
Comment 1 Matt MacIvor CLA 2011-08-09 15:01:32 EDT 
Created attachment 201169 [details]
Proposed fix and tests
Comment 2 Matt MacIvor CLA 2011-08-10 11:24:37 EDT 
Attached patch checked into 2.3.1 and Trunk streams in SVN
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:10:00 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:17:12 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink