incubator-celix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jorge SANCHEZ (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CELIX-77) Configuration Admin Implementation - Beginning
Date Sat, 10 Aug 2013 11:58:47 GMT

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

Jorge SANCHEZ updated CELIX-77:
-------------------------------

    Attachment: CELIX-77_config_admin.zip
    
> 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
>
>
> Hi all. 
> I want to contribute a first humble implementation of the Configuration Admin service.
Here some comments of what's is capable of this implementation; I do recommend to have some
knowledge of the service to understand them. 
> Currently it's implemented the next public classes: ConfigurationAdmin, ManagedService
and Configuration. Not all the functionality of those classes is done, there is still work
to do. 
> From the point of view of the API's user, the current implementation deals only with
ManagedService targets and the user can create a new Configuration objects, get an existing
Configuration or update the Configuration through the method configuration.update() which
triggers asynchronous callbacks to the ManagedService implementation. The concept of visibility
between bundles and bindings between ManagedService targets and Configurations is solved,
but due to the Configuration Permission class is not implemented yet, everything is allowed
or authorized and nothing is restricted.
> The code of the service is quite clean, except for, perhaps, the “overwhelming of printf's”
that I used to help me in the debugging and that I haven't removed yet. Another issue of this
is, there is a folder with some “dummy” examples that I use and modify constantly 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 them 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. 
> I'm newbie with CELIX and I'm completely lost with the licenses, procedures, etc, …,
please any incoming from you it's welcome.
> I don't want to make larger this email to avoid confusion. Please, if you any doubts,
I'd be pleased to answer them, don't hesitate to write 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 ignore or do it in another different
way

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message