| Summary: | org.eclipse.emf.internal.cdo.bundle.Activator activates CDOPackageTypeRegistryImpl during deactivation | ||
|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Victor Roldan Betancort <vroldanbet> |
| Component: | cdo.core | Assignee: | Project Inbox <emf.cdo-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | stepper, vroldanbet |
| Version: | 2.0 | ||
| Target Milestone: | M6 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 265435 | ||
| Bug Blocks: | |||
It's possible that we won't need the package type registry after we re-introduced legacy models. I'd like to postpone this decision until legacy models work properly. Legacy models have high priority. Do you think that I need to spend time now how to optimize what you observed? Eike, no it's not urgent, I prefer you to put efforts in Legacy models :) Fixed in bug 265435 Fix available in EMF CDO 2.0.0M6b Generally available. |
protected void doStop() throws Exception { CDOViewProviderRegistryImpl.INSTANCE.deactivate(); CDOPackageTypeRegistryImpl.INSTANCE.deactivate(); } if CDOPackageTypeRegistryImpl wasn't activated, it will be, and then deactivated. CDOPackageTypeRegistryImpl does a lot of stuff during its activation. Is it possible to avoid activation of this class if it wasn't necesary during bundles lifecycle?