Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364158 - Performance Improvement - Only create SAXParserFactory when SAX is used when Unmarshalling
Summary: Performance Improvement - Only create SAXParserFactory when SAX is used when ...
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-11-18 09:38 EST by Blaise Doughan CLA
Modified: 2022-06-09 10:23 EDT (History)
1 user (show)

See Also:


Attachments
Core - Fix (10.09 KB, patch)
2011-11-18 09:41 EST, Blaise Doughan CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Blaise Doughan CLA 2011-11-18 09:38:08 EST
Currently a SAXParserFactory is created per Unmarshaller even when a SAX parser is not used during the unmarshal operation.
Comment 1 Blaise Doughan CLA 2011-11-18 09:41:40 EST
Created attachment 207218 [details]
Core - Fix
Comment 2 Blaise Doughan CLA 2011-11-18 11:16:16 EST
Fix checked into 2.3.2 at rev:  10423

Code reviewed by:  Denise Smith

Fix Details:
A SAXParserFactory is now only created when required.  

NOTE
Starting with EclipseLink 2.4.0 there is only a single instance of SAXParserFactory that is not lazily initialized.
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:23:03 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink