|Re: [ecf-dev] Tooling|
Hi All,I don't disagree with any of this...I would like to see much more.
On 7/2/2013 9:16 AM, Wim Jongman wrote:
We should make tooling that hooks into PDE. I think this was mentioned on the last call.
I am thinking about the following tasks:
1. Create a remote services client
with options for the protocol and discovery
2. Create a remove services discovery server
with options for the discovery proto
It would create stubs for a server, create all the components and settings, makes tycho artifacts in different projects. All components would be ready to deploy or use.
That would also make a great topic for the ECF talk.
FWIW, I did add a PDE template in ECF 3.6.0 for remote services..and it's in ECF/3.6.1 of course. With ECF installed, if one creates a plugin project, selects 'an OSGi Framework'->Next and selects 'Generate an activator...'->Next there are two templates from ECF remote services (along with the others contributed by PDE): OSGi Remote Service Host Example and OSGi Remote Service Consumer Example. These create host and consumer projects, respectively...generating some simple java source in the Activator (to register host, and to lookup via ServiceTracker on client).
Just so everyone is aware, all of the code for these templates is in this plugin:
There are plenty of additions possible here...along the lines that Wim has outlined...e.g.
a) add the creation of build info (PDE and/or Tycho...I'm not really partial on which ones myself)...e.g. feature(s), product configs, etc...so that the projects can be easily built and deployed
b) add other ways of registering/exporting and discovering/importing remote services (e.g. DS)
c) add PDE wizard pages to configure the discovery provider and the distribution provider...with the appropriate options as Wim points out.
I'm not going to be able to work on this myself in the next few weeks, but I will/can support others in working on it, if there are contributions. I would actually like to see several new/other pde templates...rather than modifying the existing one (although enhancing/modifying the existing one is ok with me too).
As for topic for ECF talk...yes, I agree.
ecf-dev mailing list
Back to the top