| Summary: | OCL.initialize is inadequate | ||
|---|---|---|---|
| Product: | [Modeling] OCL | Reporter: | Ed Willink <ed> |
| Component: | Core | Assignee: | OCL Inbox <mdt-ocl-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipse |
| Version: | 3.1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Ed Willink
Ed, what exactly do you mean with "ignores delegates?" (In reply to comment #1) > Ed, > > what exactly do you mean with "ignores delegates?" The delegates are registered via extension points. This is not replicated in the initialize(). From DelegatesTest at least String oclDelegateURI = OCLDelegateDomain.OCL_DELEGATE_URI; EOperation.Internal.InvocationDelegate.Factory.Registry.INSTANCE.put (oclDelegateURI, new OCLInvocationDelegateFactory.Global()); EStructuralFeature.Internal.SettingDelegate.Factory.Registry.INSTANCE.put (oclDelegateURI, new OCLSettingDelegateFactory.Global()); EValidator.ValidationDelegate.Registry.INSTANCE.put (oclDelegateURI, new OCLValidationDelegateFactory.Global()); QueryDelegate.Factory.Registry.INSTANCE.put (oclDelegateURI, new OCLQueryDelegateFactory.Global()); I see. Probably a post-Helios change since this clearly changes initialize()'s behavior. (In reply to comment #3) > I see. Probably a post-Helios change since this clearly changes initialize()'s > behavior. Absolutely. (post-Indigo). There are now OCLDelegateDomain.initialize routines to initialize delegates. With code generation rendering all bar Query delegates obsolete, there seems little point enforcing unnecessary initialization. CLOSED after a year in the RESOLVED state. |