Hi,

I second Achim for the -f: it's exactly the purpose of this option.

Regards
JB

On 03/26/2013 09:42 PM, Achim Nierbeck wrote:
Hi,

you should add the '-f' to the config:edit command, this way a file with
the same name is created.
In your case it should look like the following:

config:edit -f com.mycompany.myservice-healthcheck

regards, Achim



2013/3/26 Gareth <[email protected]
<mailto:[email protected]>>

    Hi,

    I am trying to update factory config via config: commands (Karaf 2.3.1).
    This config was created by an entry in a feature file thus a backing
    config
    file does not exist. i.e.:

    Pid:
      com.mycompany.myservice.327d4cd4-4704-4190-9e51-26f5f0b91435
    FactoryPid:     com.mycompany.myservice
    BundleLocation: mvn:com.mycompany/mycompany/1.0.0-SNAPSHOT
    Properties:
        myservice.host = 0.0.0.0
        myservice.port = 8080
        org.apache.karaf.features.configKey =
    com.mycompany.myservice-healthcheck
        service.factoryPid = com.mycompany.myservice
        service.pid =
    com.mycompany.myservice.327d4cd4-4704-4190-9e51-26f5f0b91435

    If I try and edit this config. e.g.:

    config:edit com.mycompany.myservice-healthcheck
    config:propset myservice.port = 8081
    config:update

    I get a new config:

    Pid:
      com.mycompany.myservice.8cbfea87-f66e-44b4-b94a-11fdb14c235f
    FactoryPid:     com.mycompany.myservice
    BundleLocation:
    mvn:com.antennasoftware/gravity.clientAP.blueprint/1.0.0-SNAPSHOT
    Properties:
        service.pid =
    com.mycompany.myservice.8cbfea87-f66e-44b4-b94a-11fdb14c235f
        myservice.port = 8081
        service.factoryPid = com.mycompany.myservice
        felix.fileinstall.filename =
    
file:/home/karaf/apache-karaf-2.3.1/etc/com.mycompany.myservice-healthcheck.cfg

    If I go and specify the pid exactly:

     > config:edit
    com.mycompany.myservice.327d4cd4-4704-4190-9e51-26f5f0b91435
     > config:propset myservice.port 8081
     > config:update

    Nothing happens. Am I missing something here?

    BTW, if the factory configuration is backed by a file everything
    works fine.
    And if I update a non-factory not backed by a file, a file gets created
    after the update.

    If someone could let me know what I am doing wrong, it would be much
    appreciated.

    thanks in advance,
    Gareth





    --
    View this message in context:
    
http://karaf.922171.n3.nabble.com/Updating-Managed-Service-Factory-Config-Via-config-commands-tp4028322.html
    Sent from the Karaf - User mailing list archive at Nabble.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/>

--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to