Bug 468651 - Provide custom adapter factories via meta model services
Summary: Provide custom adapter factories via meta model services
Status: CLOSED WONTFIX
Alias: None
Product: Sphinx
Classification: Automotive
Component: Navigator & Editor Sockets (show other bugs)
Version: 0.9.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Ali AKAR CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-28 11:14 EDT by Ali AKAR CLA
Modified: 2024-05-07 00:53 EDT (History)
3 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 Ali AKAR CLA 2015-05-28 11:14:05 EDT 
The use of a custom adapter factory is spread out in different components/classes:
- org.eclipse.sphinx.emf.explorer.BasicExplorerContentProvider.getCustomAdapterFactory()
- org.eclipse.sphinx.emf.explorer.BasicExplorerLabelProvider.getCustomAdapterFactory()
- org.eclipse.sphinx.emf.explorer.actions.providers.BasicModelEditActionProvider.getCustomAdapterFactory()

Instead of returning null as default implementation, we should try to get a service contributed by the application to return the custom adapter factory (service interface need to be defined in Sphinx).

So the applications will only contribute a service instead of extending all the mentioned classes to override the #getCustomAdapterFactory.
Comment 1 Balazs Grill CLA 2024-05-07 00:53:30 EDT 
Closed stale issue before migration