Skip to content
This repository has been archived by the owner on May 7, 2020. It is now read-only.

Deprecate & deactivate DiscoveryServiceCallback and ExtendedDiscovery… #6237

Merged

Conversation

htreu
Copy link
Contributor

@htreu htreu commented Sep 19, 2018

…Service

Fixes #6216.

Signed-off-by: Henning Treu henning.treu@telekom.de

@cdjackson
Copy link
Contributor

cdjackson commented Sep 19, 2018 via email

@lolodomo
Copy link
Contributor

And this should be tagged as API breaking ?

Copy link
Contributor

@kaikreuzer kaikreuzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few small comments

@@ -24,25 +23,30 @@
* <p>
* This interface must not be implemented by bindings.
*
* @deprecated The use of this callback is deprecated. The {@link Inbox} should be able to deal with updates.
* Incremental discovery should be handled internaly by each {@link DiscoveryService}.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: internaly

@@ -24,25 +23,30 @@
* <p>
* This interface must not be implemented by bindings.
*
* @deprecated The use of this callback is deprecated. The {@link Inbox} should be able to deal with updates.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"should be able" -> "is able"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking about a custom Inbox implementation. But you a re right, ESH offers this behaviour. Will change.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you want to address any implementation, you can also say "must be able".

@@ -21,9 +21,14 @@
* The {@link DiscoveryService} will get a {@link DiscoveryServiceCallback}, which provides the extended framework
* capabilities.
*
* @deprecated The extended access to the core framework was misused most of the time and will be removed in a later
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the main reason for deprecation is the cyclic dependency. You should not make our consumers feel guilty about it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, you a re right. I re-wrote this sentence 3 times. will change.

…Serice

Fixes eclipse-archived#6216.

Signed-off-by: Henning Treu <henning.treu@telekom.de>
@htreu htreu force-pushed the 6216_deprecate_ex_discovery_service branch from 7d3df0b to 5d5652b Compare September 24, 2018 10:21
Signed-off-by: Henning Treu <henning.treu@telekom.de>
Copy link
Contributor

@kaikreuzer kaikreuzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Henning Treu added 2 commits September 27, 2018 11:09
Signed-off-by: Henning Treu <henning.treu@telekom.de>
Signed-off-by: Henning Treu <henning.treu@telekom.de>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants