Hi Krzysztof,

config:edit should do the trick straight forward using the ConfigAdmin persistence. However, I don't see the persistence adapter call (I remember that Christian did a change around that).

I gonna create a Jira about that and fix that for 3.0.1.

Regards
JB

On 12/26/2013 03:15 AM, Krzysztof Sobkowiak wrote:
Hi

How can I force to create the config file in etc using
config:edit/config:update with nonexisting pid in 3.0.0? I tried to add
the felix.fileinstall.filename property but the file is not created.

Best regards
Krzysztof

On 25.06.2013 10:17, Achim Nierbeck wrote:
ahh, yes that's the property one needs ... (and I was looking for ...)
so basically it should already do if one supplies this property in the
config element,
wouldn't it?
So basically we should close that issue with a little bit of
documentation :-)
If this property

felix.fileinstall.filename=foo.bar.cfg

is applied it'll be written to the etc folder

need to test it but it might work right away ;)


regards, Achim


2013/6/25 Jean-Baptiste Onofré <j...@nanthrax.net <mailto:j...@nanthrax.net>>

    It does that if the FileInstall felix.fileinstall.filename
    property exist in the configuration PID.

    For the config element, we can do exactly as we do in
    config:update command and Config MBean.

    Regards
    JB


    On 06/25/2013 08:52 AM, Christian Schneider wrote:

        Currently config admin keeps track if the config was
        originally read
        from a file. If yes then changes are also written back to the
        original file.
        If no then changes are only done in memory.

        So I think it would make sense to have an option on the config
        element
        to decide if it should be persisted to a file. Unfortunately
        this means
        that we have to do more than just call the config admin in
        this case.


        Chrisitan

        Am 24.06.2013 16:20, schrieb Lothar Werzinger:


            I think it should at least create the file when the data
            is modified
            via config amin (e.g. the web interface). Creating it on
            feature
            install is a bonus, but not strictly necessary

            Lothar Werzinger

            Sent from a mobile device.


            This message and any attachment (the "message") is
            intended solely for
            the addressees and is confidential. If you receive this
            message by
            mistake, please delete it and notify the sender
            immediately. Any use
            not in accordance with its purpose, any out-spread or
            disclosure,
            either as a whole or partially, is prohibited except with
            formal
            approval. Internet cannot guarantee the integrity of this
            message,
            therefore Tradescape will not be liable for the message if
            modified.

            -



        --

        Christian Schneider
        http://www.liquid-reality.de

        Open Source Architect
        Talend Application Integration Divisionhttp://www.talend.com
        <http://www.talend.com>


    --
    Jean-Baptiste Onofré
    jbono...@apache.org <mailto:jbono...@apache.org>
    http://blog.nanthrax.net
    Talend - http://www.talend.com




--

Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
Committer & Project Lead
OPS4J Pax for Vaadin
<http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project
Lead
blog <http://notizblog.nierbeck.de/>


--
Krzysztof Sobkowiak

JEE & OSS Architect | Technical Architect @ Capgemini
e-mail: krzys.sobkow...@gmail.com <mailto:krzys.sobkow...@gmail.com> |
Twitter: @KSobkowiak

--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to