Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327318 - Provide an optimized mechanism to determine an EEnumLiteral from an Enumerator value instance
Summary: Provide an optimized mechanism to determine an EEnumLiteral from an Enumerato...
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.core (show other bugs)
Version: 4.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Eike Stepper CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard: Lighter, Faster and Better
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-08 05:26 EDT by Eike Stepper CLA
Modified: 2011-06-23 03:39 EDT (History)
0 users

See Also:

Attachments
Patch v1 - for future reference (3.77 KB, patch)
2010-10-08 05:27 EDT, Eike Stepper 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 Eike Stepper CLA 2010-10-08 05:26:34 EDT 
For a given Enumerator value like Vat.VAT15 it is not easily possible to determine the associated EEnumLiteral in the meta model.

CDOPackageRegistry should lazily populate a cache for Enumerator-->EEnumLiteral mappings.
Comment 1 Eike Stepper CLA 2010-10-08 05:27:56 EDT 
Created attachment 180479 [details]
Patch v1 - for future reference
Comment 2 Eike Stepper CLA 2010-10-08 05:28:15 EDT 
Committed to HEAD
Comment 3 Eike Stepper CLA 2010-10-08 08:05:35 EDT 
See  CDOPackageRegistry:

 /**
   * @since 4.0
   */
  public EEnumLiteral getEnumLiteralFor(Enumerator value);
Comment 4 Eike Stepper CLA 2011-06-23 03:39:23 EDT 
Available in R20110608-1407