[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Implementing plugin using service model
|
That's pretty much it.
You don't need IServiceProviderConfiguration, as it was only added for
the transition from RDT. I'm not sure IServiceContributor is going to
end up being used, but it can't hurt to have it there.
You should be at least seeing your service and provider showing up in
the UI.
Greg
On Sep 24, 2009, at 2:06 PM, Dave Wootton wrote:
I'm looking at the changes for a plugin I'm working on to work with
the
service model. This plugin will implement a new service. I've
updated the
plugin.xml to add extensions for
org.eclipse.ptp.services.core.services,
org.eclipse.ptp.services.core.providers,
org.eclipse.ptp.services.ui.providerContributors and
org.eclipse.ptp.services.core.ui.serviceContributors
I've implemented classes for each class expected by these extensions,
although at the moment, these are just stubs for the required
implementatoons of abstract methods for each class. I have classes
that
implement IServiceProviderContributor, IServiceContributor,
IServiceProviderConfiguration (which is marked deprecated) and a class
which extends ServiceProvider and currently only includes a stub
isConfigured() method
Is there more that I need to do, or that I should not be doing?
Is there a set of classes you suggest as an example of what I should
implement?
Thanks
Dave
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
