Bug 351454 - [NLS] Usage of NLS makes the EAP not directly useable in Multi-Instance/Multi-Locale env
Summary: [NLS] Usage of NLS makes the EAP not directly useable in Multi-Instance/Multi...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-07 10:26 EDT by Thomas Schindl CLA
Modified: 2011-07-07 15:21 EDT (History)
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 Thomas Schindl CLA 2011-07-07 10:26:48 EDT 
We are currently using NLS which loads our translated strings into static-fields. While this approach is fine for an RCP/SDK-Env it breaks for Multi-Instance/Multi-Locle environments which RAP is one for example.

This means RAP will have to patch e4-bundles to support this which IMHO is not correct solution. We always defined that statics/singletons are evil in e4 and so we need find another/better solution to the problem.

My suggestion would be to adopt the translation story provided by the e4-bridge which works on an instance base and an in memory cache