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

Róbert Csákány commented on FELIX-2100:
---------------------------------------

Configloader don't depends on FileInstall package.  I reused some code from it 
(and some pattern from Sling content loader), my bundle operates only two other 
bundle, ConfigAdmin and LogService (optional) - So it's a separate bundle. 
There was no point to integrate my code to fileinstall because I used only the 
config parser and some util function from it - too much refactoring in 
fileinstall is needed to integrate.

I've checked the possibility the usage of API, but for me it was not clear how 
can I bind the ResourceProcessor to the bundle content. As I understand in the 
code the ResourceProcesor couldn't operate without DeploymentAdmin package. The 
ResourceProcessors connects with DeploymentAdmin bundle with several points - 
to follow the DeploymentAdmin lifecycle and the content loading based on 
DeploymentSession as OSGI interfaces describes - the DeploymentAdmin calls 
ResourceProcessor over Command interface). 

Maybe It can be make a new prototype for  a content calllback mechanism where 
BundleContentCallbackProcessor services are registered - but it's not so simple 
because the bundles lifecycle (cancel and rollback mechanism) - if I have some 
time I will analyze the possibilities. - I need time to understand OSGi and 
Felix API in deep.

You have to understand I'm very new in this OSGi world and I have big black 
holes in my knowledge. I need a fast, independent solution.

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

Reply via email to