Eclipse Community Forums: DSDP - Tools for Mobile Linux (TML) » Why have two extension-points to define services

Help

Home

Home » Archived » DSDP - Tools for Mobile Linux (TML) » Why have two extension-points to define services

Show: Today's Messages :: Show Polls :: Message Navigator

Why have two extension-points to define services [message #561809]

Wed, 23 July 2008 19:05

Daniel Guimaraes

Messages: 4
Registered: July 2009

Junior Member

Hello everyone,

I am not sure I got the idea of having the two different extension-points
to define services (org.eclipse.tml.framework.device and
org.eclipse.tml.serviceDefinition)

My understanding is that the goal of having two extension points is
basically defining basic service information through
"org.eclipse.tml.framework.device" and allowing them to be customized by
the "org.eclipse.tml.serviceDefinition" (which also defines handlers for
the state transitions).
This way one plug-in can define the services available and other plug-ins
could provide the different "implementation" for that same service.

Did I get the idea?

If my understanding is correct I would like to suggest merging these two
extension points in one (in order to avoid confusion) and add the
capability of defining services as abstract and allowing services to
extend parent services (something similar to what CDT does with elements
of the org.eclipse.cdt.managedbuilder.core.buildDefinitions)

Thanks,

Daniel

Report message to a moderator