felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-2100) Initial Config Loader
Date Sun, 21 Feb 2010 05:50:28 GMT

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

Richard S. Hall commented on FELIX-2100:

Yeah, for a quick and dirty solution you are probably on the right track, but I haven't looked
at your implementation so I cannot say if it is done in the best way.

Also, I am not saying your bundle depends on File Install, I am wondering if it has enough
synergy to become part of File Install. Earlier you complained about having to deploy too
many bundles to get the desired functionality, so this comment is more directed at that.

Still, I am more thinking about how to handle the generic issue. OBR deploys resources, but
currently it only knows how to process bundle resources. Other types of resources are installed,
but have no follow on activity. If we assume that every processor, like yours, follows the
extender pattern like yours, then maybe this is sufficient since they will just jump to action
once a resource of their type is installed.

However, I was wondering if there is some generic layer here, like what Deployment Admin offers
with Resource Processors. If that API is too tied to DA, then we don't need to use it, but
its concepts are still valid, so can they be reused? Would it be worthwhile?

> 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.
You can reply to this email to add a comment to the issue online.

View raw message