felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-2100) Initial Config Loader
Date Mon, 31 Dec 2012 20:24:12 GMT

    [ https://issues.apache.org/jira/browse/FELIX-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541492#comment-13541492
] 

Felix Meschberger commented on FELIX-2100:
------------------------------------------

This is quite dated.

I am also not sure what to make of it: For one thing I think relating the life cycle of a
bundle with the "life cycle" of configuration is conceptually wrong. Also the creators are
generally (conceptually) different: A bundle is created by a developer while configuration
is created and managed by a systems administrator (even though default configuration might
be provided by a developer).

IMHO approaches like those provided by the Felix File Install or Sling OSGi Installer are
 more appropriate. 
                
> Initial Config Loader
> ---------------------
>
>                 Key: FELIX-2100
>                 URL: https://issues.apache.org/jira/browse/FELIX-2100
>             Project: Felix
>          Issue Type: New Feature
>          Components: Bundle Repository (OBR), Configuration Admin
>            Reporter: Róbert Csákány
>         Attachments: configloader.zip
>
>
> I've a request to be able to make customer specific configuration bundles - bundles that
includes Configurations for other bundles. If a bundle is deployed, extracts the configuration
files and register it with configadmin. If bundle is removed, removes configurations. If you
have ideas, please share it! (I'm new in this Felix world, I've used it only with Sling as
a user)
> I will make a short proporsal and a whiteboard implementation.
> The name of impmelemtation is configloader
> The configloader service will implement the SynchronousBundleListener, and registering
itself in activation and unregistering in deactivation.
> When a new bundle is registering, checking the Bundle-InitialConfigurations in META-INF/MANIFEST.MF
file. If the entry is presented, checking the given folders for *.xml files describes the
configurations entry. (To handle the Factory services also).
> Is it correct?

--
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