You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@celix.apache.org by "Pepijn Noltes (JIRA)" <ji...@apache.org> on 2016/10/10 09:58:22 UTC
[jira] [Closed] (CELIX-136) [contrib] Configured endpoint discovery
[ https://issues.apache.org/jira/browse/CELIX-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pepijn Noltes closed CELIX-136.
-------------------------------
> [contrib] Configured endpoint discovery
> ---------------------------------------
>
> Key: CELIX-136
> URL: https://issues.apache.org/jira/browse/CELIX-136
> Project: Celix
> Issue Type: Bug
> Components: Remote Service Admin
> Reporter: J.W. Janssen
> Assignee: Alexander Broekhuis
> Labels: patch
> Fix For: next
>
> Attachments: 0001-Implementing-configured-discovery.patch, 0001-Some-fixes-and-review-comments-processed.patch
>
>
> I've implemented a configured discovery implementation for use with Celix remote services, similar as the one provided by Amdatu Remote (see https://amdatu.atlassian.net/wiki/display/AMDATUDEV/Amdatu+Remote) and want to contribute this code back to the Celix project.
> The configured discovery allows you to define "static" endpoints where the discovery service can query the set with available services. In addition, it runs a small web-server that allows other configured discovery implementations to query for the locally exported services.
> If necessary I'm willing to maintain this code in the near future.
> (legal stuff: the code was written with consent of my employer and I'm already an Apache committer & member, so there should be no need for an CLA)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)