Mailing-List: contact celix-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: celix-dev@incubator.apache.org
Date: Tue, 15 Oct 2013 19:20:47 +0000 (UTC)
From: "Pepijn Noltes (JIRA)" <jira@apache.org>
To: celix-commits@incubator.apache.org
Message-ID: <JIRA.12663037.1376135759862.67913.1381864847519@arcas>
In-Reply-To: <JIRA.12663037.1376135759862@arcas>
References: <JIRA.12663037.1376135759862@arcas>
Subject: [jira] [Updated] (CELIX-77) Configuration Admin Implementation -
 Beginning
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CELIX-77?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Pepijn Noltes updated CELIX-77:
-------------------------------

    Attachment: CELIX-77_config_admin.zip.md5

md5 sum for the config_admin patch to identify it for the grant.

> Configuration Admin Implementation - Beginning
> ----------------------------------------------
>
>                 Key: CELIX-77
>                 URL: https://issues.apache.org/jira/browse/CELIX-77
>             Project: Celix
>          Issue Type: New Feature
>    Affects Versions: 0.0.1-incubating
>            Reporter: Jorge SANCHEZ
>            Priority: Minor
>              Labels: patch
>         Attachments: CELIX-77_config_admin.zip, CELIX-77_config_admin.zip=
.md5
>
>
> Hi all.=20
> I want to contribute a first humble implementation of the Configuration A=
dmin service. Here some comments of what's is capable of this implementatio=
n; I do recommend to have some knowledge of the service to understand them.=
=20
> Currently it's implemented the next public classes: ConfigurationAdmin, M=
anagedService and Configuration. Not all the functionality of those classes=
 is done, there is still work to do.=20
> From the point of view of the API's user, the current implementation deal=
s only with ManagedService targets and the user can create new Configuratio=
n objects, get an existing Configuration or update the Configuration throug=
h the method configuration.update() which triggers asynchronous callbacks t=
o the ManagedService implementation. The concept of visibility between bund=
les and bindings between ManagedService targets and Configurations is solve=
d, but due to the Configuration Permission class is not implemented yet, ev=
erything is allowed or authorized and nothing is restricted.
> The code of the service is quite clean, except for, perhaps, the =E2=80=
=9Coverwhelming of printf's=E2=80=9D that I used to help me in the debuggin=
g and that I haven't removed yet. Another issue of this is, there is a fold=
er with some =E2=80=9Cdummy=E2=80=9D examples that I use and modify constan=
tly for debugging, I must recognize that they are not very clean and I don'=
t know if someone can understand something, but I've decided to included th=
em because may be someone can find them useful.
> Finally, as I appointed, there is still much work to do, but I hope with =
my contribution give a first light in the development of the service.=20
> I'm newbie with CELIX and I'm completely lost with the licenses, procedur=
es, etc, =E2=80=A6, please any incoming from you it's welcome.
> I don't want to make larger this email to avoid confusion. Please, if any=
 of you have any doubts, I'd be pleased to answer them, don't hesitate to w=
rite me.
> Friendly greetings,
> Jorge SANCHEZ
> P.S.: in the private directory there is a "framework patch", I had to do =
it because I was missing some functions in the framework that I could not i=
gnore or do it in another different way


--
This message was sent by Atlassian JIRA
(v6.1#6144)