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:43 GMT

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

Michael Van Geertruy commented on KARAF-418:
--------------------------------------------

>From Pieber on the mailing list:

To avoid hooking jamies thread here an answer one point to karafman's point in a 
different thread: 

I would like to have default option for databasing :) BUT, I don't like that 
karaf uses jdbc directly. Since most of my projects are based on aries-jpa it 
would be cool to somehow integrate this into the JPA infrastructure. I'm not 
completely sure how this could be done (requrired bundles, startup order, ...) 
but it would be quite cool to not e.g. autogenerate the schema for the tables. 

Any ideas according to this topic? 

kind regards, 
andreas 



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


Mime
View raw message