Eclipse Community Forums: Eclipse Communications Framework (ECF) » Re: REST for ECF: declarative services?

Help

Home

Home » Archived » Eclipse Communications Framework (ECF) » Re: REST for ECF: declarative services?

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

Re: REST for ECF: declarative services? [message #475886]

Wed, 05 August 2009 23:06

Scott Lewis

Messages: 1038
Registered: July 2009

Senior Member

Ande,

Thanks for the nice words.

The REST-based work started by Holger for his summer of code project is
indeed very nice, and I expect it to make it into ECF 3.1 with
help/review/contributions from the community (like yours...thanks very
much!)

We've started the IP review process for the third-party code pieces of
the work (i.e. the json.org json parser)...and as soon as the GSOC
project is over I will be looking to include in ECF 3.1 (Sept release).
Between now and then (Sept) I would *very* much appreciate all the
review/improvement suggestions that people can/could make so that when
it goes out it is as production-ready as possible.

Again thanks for the help...I think that in combination with the ECF
remote services work, along with the RFC119 implementation work (built
on remote services API so the REST providers will slip in underneath
with no additional effort) this is a very exciting direction.

Scott

Ande Dietisheim wrote:
> Hi!
>
> I started using the REST Abstraction for ECF that was developed @ GSoC.
> Quite promising so far! Keep up the great work!
> I use json-based mashalling and I noticed that I have to autostart
> org.eclipse.ecf.remoteservice.rest.resource.json in order to have a
> corresponding resource reprasantation ready for ECF. I guess this is due
> to the programmatic service registration that occurs in the bundle
> activator. We'd get rid of that if we'd use declarative services. Am I
> missing something? I'd be happy to contribute that!
>
> Cheers
> André

Report message to a moderator

Re: REST for ECF: declarative services? [message #478674 is a reply to message #475886]

Thu, 06 August 2009 11:18

Andre Dietisheim

Messages: 131
Registered: July 2009

Senior Member

Hi Scott

thanks for those enligthments :-) RFC119 sounds very interesting, indeed.
By chance I got a project where ECF Rest's a perfect match and I startet
using it (CDO would have been a perfect match too, but those guys
implement the server and didn't want to change to CDO though). No doubt,
I'll report all bugs/enhancements I figure out!
I'd be very happy if my patches could get reviewed and committed/corrected:

DS for ResourceRepresentations:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=285294

Request body for POST:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=285256

That would allow me to get on with ECF without too many patches to care for.
Could you please give me some hints how to handle these patches? I need
them in my project-SCM, wouldn't like to cut the link to the ECF-CVS (If
I'm not mistaken, I cannot share projects in 2 SCM) either. Is including
them in my target-platform only a good idea? What are your best
practices here?

Thanks + Cheers
André

Scott Lewis wrote:
> Ande,
>
> Thanks for the nice words.
>
> The REST-based work started by Holger for his summer of code project is
> indeed very nice, and I expect it to make it into ECF 3.1 with
> help/review/contributions from the community (like yours...thanks very
> much!)
>
> We've started the IP review process for the third-party code pieces of
> the work (i.e. the json.org json parser)...and as soon as the GSOC
> project is over I will be looking to include in ECF 3.1 (Sept release).
> Between now and then (Sept) I would *very* much appreciate all the
> review/improvement suggestions that people can/could make so that when
> it goes out it is as production-ready as possible.
>
> Again thanks for the help...I think that in combination with the ECF
> remote services work, along with the RFC119 implementation work (built
> on remote services API so the REST providers will slip in underneath
> with no additional effort) this is a very exciting direction.
>
> Scott
>
> Ande Dietisheim wrote:
>> Hi!
>>
>> I started using the REST Abstraction for ECF that was developed @
>> GSoC. Quite promising so far! Keep up the great work!
>> I use json-based mashalling and I noticed that I have to autostart
>> org.eclipse.ecf.remoteservice.rest.resource.json in order to have a
>> corresponding resource reprasantation ready for ECF. I guess this is
>> due to the programmatic service registration that occurs in the bundle
>> activator. We'd get rid of that if we'd use declarative services. Am I
>> missing something? I'd be happy to contribute that!
>>
>> Cheers
>> André
S

Report message to a moderator

Re: REST for ECF: declarative services? [message #478790 is a reply to message #478674]

Thu, 06 August 2009 22:16

Scott Lewis

Messages: 1038
Registered: July 2009

Senior Member

Hi Ande,

Ande Dietisheim wrote:
> Hi Scott
>
>
> thanks for those enligthments :-) RFC119 sounds very interesting, indeed.

Yes. I'm not sure if I made clear previously but just in case: once a
REST provider is created that implements the ECF remote services API,
then the existing RFC119 impl will work transparently...as the ECF
RFC119 impl will work with any remote services API provider (including a
REST based one).

> By chance I got a project where ECF Rest's a perfect match and I startet
> using it (CDO would have been a perfect match too, but those guys
> implement the server and didn't want to change to CDO though). No doubt,
> I'll report all bugs/enhancements I figure out!
> I'd be very happy if my patches could get reviewed and committed/corrected:
>
> DS for ResourceRepresentations:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=285294
>
> Request body for POST:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=285256
>
> That would allow me to get on with ECF without too many patches to care
> for.
> Could you please give me some hints how to handle these patches?

Since Holger is the lead for the ECF REST work (as he initiated it with
his Google SOC project), it is his decision to decide whether/when/how
to incorporate community contributions.

I would encourage you to communicate on the respective bugs with Holger
to get his thoughts on both of the bugs. I will offer my assistance and
support to Holger (and to you) if desired (i.e. I can/could help
incorporate the contributions, help with testing, etc).

I'm very hopeful that the ECF REST API work will be moved quickly into
the ECF distribution (hopefully as soon as ECF 3.1 in Sept).

I need
> them in my project-SCM, wouldn't like to cut the link to the ECF-CVS (If
> I'm not mistaken, I cannot share projects in 2 SCM) either. Is including
> them in my target-platform only a good idea? What are your best
> practices here?

Since I believe both of your contributions are generalizations to handle
your use case (and others), I think that they probably do belong in the
ECF REST API itself...i.e. committed to the CVS location on the OSU Open
Source Lab CVS server), but again I leave the final word on that
decision to Holger. If there are some things that need to move into or
be added to the ECF remote service API, or the ECF core API as well, I
will happily effect those changes myself (after we jointly figure out if
they are needed/what they are).

So I suggest that we continue this dialog on the ecf-dev mailing list
and the two bugs (rather than the newsgroup), and engage Holger directly
as it's getting pretty technical and detailed...and I don't believe that
Holger monitors the ECF newsgroup as regularly.

Thanksinadvance for your contributions Andre. We will certainly find a
way to support your usage here...and appreciate your patience. The ECF
REST work is brand new (Holger's GSOC project is not even finished
yet!), but we will be moving quickly to mature it and get it distributed
as part of ECF.

Scott

>
> Thanks + Cheers
> André
>
> Scott Lewis wrote:
>> Ande,
>>
>> Thanks for the nice words.
>>
>> The REST-based work started by Holger for his summer of code project
>> is indeed very nice, and I expect it to make it into ECF 3.1 with
>> help/review/contributions from the community (like yours...thanks very
>> much!)
>>
>> We've started the IP review process for the third-party code pieces of
>> the work (i.e. the json.org json parser)...and as soon as the GSOC
>> project is over I will be looking to include in ECF 3.1 (Sept
>> release). Between now and then (Sept) I would *very* much appreciate
>> all the review/improvement suggestions that people can/could make so
>> that when it goes out it is as production-ready as possible.
>>
>> Again thanks for the help...I think that in combination with the ECF
>> remote services work, along with the RFC119 implementation work (built
>> on remote services API so the REST providers will slip in underneath
>> with no additional effort) this is a very exciting direction.
>>
>> Scott
>>
>> Ande Dietisheim wrote:
>>> Hi!
>>>
>>> I started using the REST Abstraction for ECF that was developed @
>>> GSoC. Quite promising so far! Keep up the great work!
>>> I use json-based mashalling and I noticed that I have to autostart
>>> org.eclipse.ecf.remoteservice.rest.resource.json in order to have a
>>> corresponding resource reprasantation ready for ECF. I guess this is
>>> due to the programmatic service registration that occurs in the
>>> bundle activator. We'd get rid of that if we'd use declarative
>>> services. Am I missing something? I'd be happy to contribute that!
>>>
>>> Cheers
>>> André
> S

Report message to a moderator