Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 13537 invoked from network); 19 Feb 2010 05:21:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Feb 2010 05:21:49 -0000 Received: (qmail 97412 invoked by uid 500); 19 Feb 2010 05:21:49 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 97288 invoked by uid 500); 19 Feb 2010 05:21:49 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 97270 invoked by uid 99); 19 Feb 2010 05:21:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2010 05:21:48 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Feb 2010 05:21:48 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D3BBC234C4A9 for ; Thu, 18 Feb 2010 21:21:27 -0800 (PST) Message-ID: <1650571935.379631266556887852.JavaMail.jira@brutus.apache.org> Date: Fri, 19 Feb 2010 05:21:27 +0000 (UTC) From: "Richard S. Hall (JIRA)" To: dev@felix.apache.org Subject: [jira] Commented: (FELIX-2100) Initial Config Loader In-Reply-To: <980068749.366761266521427987.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FELIX-2100?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1283= 5594#action_12835594 ]=20 Richard S. Hall commented on FELIX-2100: ---------------------------------------- I think the OBR spec definitely intends to support other resource types, bu= t so far has only demonstrated this fact by calling the base unit of descri= ption a "resource". I have thought a little bit about this area too and I t= hink it makes sense to improve upon the situation. This will be an area I i= nvestigate when I find the time to work on OBR in more depth. My current th= ought is that we should basically adopt the ResourceProcessor approach of t= he Deployment Admin spec, but I haven't given it too much more thought than= just reaching this conclusion. :-) > 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=C3=B3bert Cs=C3=A1k=C3=A1ny > > I've a request to be able to make customer specific configuration bundles= - bundles that includes Configurations for other bundles. If a bundle is d= eployed, extracts the configuration files and register it with configadmin.= If bundle is removed, removes configurations. If you have ideas, please sh= are it! (I'm new in this Felix world, I've used it only with Sling as a use= r) > I will make a short proporsal and a whiteboard implementation. > The name of impmelemtation is configloader > The configloader service will implement the SynchronousBundleListener, an= d registering itself in activation and unregistering in deactivation. > When a new bundle is registering, checking the Bundle-InitialConfiguratio= ns in META-INF/MANIFEST.MF file. If the entry is presented, checking the gi= ven folders for *.xml files describes the configurations entry. (To handle = the Factory services also). > Is it correct? --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.