Bugzilla – Full Text Bug Listing
| Summary: | [Startup] Try to initialize injectors lazily | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Sebastian Zarnekow <sebastian.zarnekow> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 | CC: | sven.efftinge |
| Version: | 1.0.0 | Flags: | sven.efftinge:
juno+
|
| Target Milestone: | M4 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
Pushed to master. Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |
The Ui Plugins will currently create the injectors for each contained language eager on bundle#start. As this is quite costly, we should consider to use a computing map: new MapMaker().makeComputingMap(new Function<String, Injector>() { public Injector apply(String language) { return createInjectorFor(language); } }) Therefore we may have to use ResourceServiceProviderDescriptors similar to EPackageDescriptor in the respective extension point implementation. However it is worth the measure the actual performance gain prior to introducing this additional complexity. Furthermore we have to be careful with the semantic of eager singletons, e.g. the validators are not registered by means of an extension point but as a side effect upon injector creation.