karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Van Geertruy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (KARAF-418) Allow configurations (from ./etc) to be placed in a database.
Date Tue, 25 Jan 2011 23:07:44 GMT

    [ https://issues.apache.org/jira/browse/KARAF-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986750#action_12986750

Michael Van Geertruy commented on KARAF-418:

Guillaume's reply:

Unless I misunderstood, the idea is just to have the configurations 
stored in a DB right ? 
If so the scope is limited to ConfigAdmin and there are two ways to 
solve the problem: 
  * implement a back-end for the Felix ConfigAdmin (the service will 
read the data once when starting and store any change back in the DB) 
  * write a bundle that polls the DB and push data into ConfigAdmin 
My experience tells me that the second way is better, but I wouldn't 
mandate JPA for such a simple thing imho, as the schema is very simple 
and the bundle would only have to read, so it's basically a single 
SELECT operation. 

> Allow configurations (from ./etc) to be placed in a database.
> -------------------------------------------------------------
>                 Key: KARAF-418
>                 URL: https://issues.apache.org/jira/browse/KARAF-418
>             Project: Karaf
>          Issue Type: Brainstorming
>            Reporter: Michael Van Geertruy
> There's been an ongoing dialogue on the dev's mailing list to discuss whether or not
to allow configurations to be placed in a database instead of in the ./etc directory.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message