[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] Addon to ECF REST Services provider, Syndication support for REST
|
Hi Pavel,
This looks like terrific work Pavel...and if you are agreeable I would
like to propose that we add it onto ECF (the rest provider) and the ECF
examples (your code that uses it).
If you are willing to contribute this code to ECF, then what has to
happen (because of the IP process)... is:
1) I've opened this bug/enhancement:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=313044 to track this
contribution. As your question conveys, all contributions have to go
through the Eclipse IP process, and the IP process revolves around
bugs/enhancements. It's your choice as to whether you want to use this
bug or separate bugs for the example (or any test) code...assuming you
wish to contribute both the example usage and the provider code. Please
open separate enhancement request(s)...dependent upon 316044...for the
example if you wish. I do think renaming the examples to (e.g.)
org.eclipse.ecf.examples.remoteservices.rest.rss would be a good idea).
2) Attach the code contributions to this new bug(s). Then we/ECF
committers can download/try it out, test it, review it, ask questions
and for small changes, and help you finish up the required elements to
integrate with ECF...and satisfy the IP review needs (e.g. copyright
headers, etc).
3) Once 2 is done to our/your satisfaction, one of the ECF committers
will create a Contribution Questionnaire (CQ) for the contribution.
This starts the Eclipse Foundation IP review...for your new code and any
dependencies. Since your provider depends upon some orbit bundles
(com.sun.syndication and org.jdom), we will also open what are called
'piggyback' CQ's for use/reuse of these Orbit bundles. I haven't yet
looked at how your dependencies on these libs are declared in your
provider, but depending upon how you've done it it may be necessary to
change the provider metadata to use the Orbit versions of these libs.
4) Once 1, 2, and 3 are done, we will commit the contribution to the ECF
repository at dev.eclipse.org.
5) We will add the provider (and examples) to the ECF build.
6) If you wish, concurrent with the above you can/could move to become
an ECF committer. This would allow you to more easily support the code
going forward (as soon as others start using such a thing like a
provider I find it usually needs some amount of bug fixing, potentially
generalization, and new API features). It's usually much easier to do
these things if one is a committer. If you are interested in doing
this, then please contact me directly at slewis at composent.com and
we'll chat...or email...about the process for this. Even if we do this,
however, it doesn't change 1-5 wrt this contribution.
Since we are nearly at the endgame of Helios, 1-5 cannot really happen
before Helios. Even if we do 1-2 right away (which would be a good
idea, I believe), 3 will take some time, and the EF IP review people are
almost certainly swamped right now dealing with Helios-specific issues.
This isn't intended to dissuade you...it's just a warning that things
can only work so fast...especially this time of year...and there's only
so much I/others can do about that.
But with that explanation, I want to propose that we proceed right away
with 1-2 for this contribution. When we get to 3 things may slow down
slightly, but I will make sure they continue to move forward (please,
btw, feel free to nag me or others along the way for status updates as
this is one of many threads going for ECF/me right now and occasionally
pings are appreciated).
And, finally...thanks very much for the work and contribution(s)! I
think I speak for the ECF community (as well as myself) when I say:
Thanks!
Scott
Samolisov Pavel wrote:
Hello all
I added an RSS/Atom support for REST Services Provider: I made the
bundle o.e.e.remoteservices.rest.synd that contains RSS/Atom parser
based on ROME (com.sun.syndication). This bundle has folows
dependencies: com.sun.syndication and org.jdom, all this ones exists in
Eclipse Orbit project. The bundle exports package
o.e.e.remoteservices.rest.synd that contains class
SyndFeedResponseDeserializer, This deserializer can parse REST response
to SyndFeed object.
Also, I create demo bundle called
name.samolisov.ecf.remoteservices.rest.rss and demonstrate how to use
SyndFeedResonseDeserializer: gets data from rss feed and writes it's
content on console,
All bundles attached for this latter.
One question. Should I open the bug and attach this bundles (rename
name.samolisov.ecf.remoteservices.rest.rss to
o.e.e.examples.remoteservices.rest.rss) to this bug?
What do you think about it. May be this work is not necessary?
------------------------------------------------------------------------
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
