60826 – ResourceBundles are too expensive

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 60826 - ResourceBundles are too expensive

Summary: ResourceBundles are too expensive

Status:	RESOLVED DUPLICATE of bug 37712

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	3.0
Hardware:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-UI-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-05-03 17:45 EDT by Chris Laffra
Modified:	2006-03-29 11:56 EST (History)
CC List:	2 users (show)

See Also:

Attachments
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 Chris Laffra

2004-05-03 17:45:27 EDT

Omnipresent use of java.util.ResourceBundle results in an overhead of 

            roughly 10-15% of Eclipse startup time 

being spent simply in reading the keys and their values from properties files 
and store them in java.util.Hashtable instances.

Too much is burned in the process. Eclipse encourages this approach through 
all its examples, all its plugins, and all code generated by PDE. A special 
Eclipse ResourceBundle subclass should be developed to address the waste.

I know Pascal Rapicault is looking into this, but I did not see a PR for it.

Comment 1 John Arthorne

2004-05-03 19:05:46 EDT

This was on the 3.0 plan from day one, but unfortunately deferred due to lack of
resources (no pun intended). I will mark this as a duplicate of the main plan
item bug report to reduce duplication.

*** This bug has been marked as a duplicate of 37712 ***