Re: How is config admin data stored?

2013-12-25 Thread Jean-Baptiste Onofré 

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



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




--

Apache Karaf  Committer & PMC
OPS4J Pax Web 
Committer & Project Lead
OPS4J Pax for Vaadin
 Commiter & Project
Lead
blog 



--
Krzysztof Sobkowiak

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


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

Re: How is config admin data stored?

2013-12-25 Thread Krzysztof Sobkowiak 

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



-- 
Jean-Baptiste Onofré

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




--

Apache Karaf  Committer & PMC
OPS4J Pax Web  
Committer & Project Lead
OPS4J Pax for Vaadin 
 Commiter & Project 
Lead

blog 



--
Krzysztof Sobkowiak

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

Re: How is config admin data stored?

2013-06-25 Thread Jean-Baptiste Onofré 
Anyway, it would have been just a workaround:  element should 
behaves as config:update or ConfigMBean.


Regards
JB

On 06/25/2013 11:34 AM, Achim Nierbeck wrote:

Just tested it,
unfortunately it's not enough to have this property set when installing
this via features.
Therefore we still need to program something, the issue needs to stay open.

regards, Achim


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

Yup, exactly ;)

Regards
JB


On 06/25/2013 10:17 AM, 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é 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 
 


 --
 Jean-Baptiste Onofré
jbono...@apache.org 
>

http://blog.nanthrax.net
 Talend - http://www.talend.com




--

Apache Karaf  Committer & PMC
OPS4J Pax Web > Committer
& Project Lead
OPS4J Pax for Vaadin
>
Commiter & Project Lead
blog 


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




--

Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer
& Project Lead
OPS4J Pax for Vaadin 
Commiter & Project Lead
blog 


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

Re: How is config admin data stored?

2013-06-25 Thread Achim Nierbeck 
Just tested it,
unfortunately it's not enough to have this property set when installing
this via features.
Therefore we still need to program something, the issue needs to stay open.

regards, Achim


2013/6/25 Jean-Baptiste Onofré 

> Yup, exactly ;)
>
> Regards
> JB
>
>
> On 06/25/2013 10:17 AM, 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é 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
>> 
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org 
>>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
>>
>>
>> --
>>
>> Apache Karaf  Committer & PMC
>> OPS4J Pax Web 
>> >
>> Committer
>> & Project Lead
>> OPS4J Pax for Vaadin 
>> 
>> >
>> Commiter & Project Lead
>> blog 
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>



-- 

Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
OPS4J Pax for Vaadin 
Commiter & Project Lead
blog

Re: How is config admin data stored?

2013-06-25 Thread Jean-Baptiste Onofré 

Yup, exactly ;)

Regards
JB

On 06/25/2013 10:17 AM, 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é 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



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




--

Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer
& Project Lead
OPS4J Pax for Vaadin 
Commiter & Project Lead
blog 


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

Re: How is config admin data stored?

2013-06-25 Thread Achim Nierbeck 
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é 

> 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
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>



-- 

Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
OPS4J Pax for Vaadin 
Commiter & Project Lead
blog

Re: How is config admin data stored?

2013-06-25 Thread Jean-Baptiste Onofré 
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



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

Re: How is config admin data stored?

2013-06-24 Thread Christian Schneider 
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 Division http://www.talend.com

Re: How is config admin data stored?

2013-06-24 Thread Achim Nierbeck 
Through the web-interface should already be, if I remember correctly.
There used to be a special flag or property available in the webconsole for
this.

regards, Achim


2013/6/24 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.
>
> -
>



-- 

Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
OPS4J Pax for Vaadin 
Commiter & Project Lead
blog

Re: How is config admin data stored?

2013-06-24 Thread 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.

-

Re: How is config admin data stored?

2013-06-24 Thread Jean-Baptiste Onofré 

Correct, and it's a pita that I forgot it: I created this Jira ;)

Regards
JB

On 06/24/2013 03:50 PM, Achim Nierbeck wrote:

Hi JB,
I think we have a issue for that, and it should be an optional feature :)
https://issues.apache.org/jira/browse/KARAF-545

regards, Achim


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

Thanks Achim, you are right, I forgot to mention the cache folder ;)

Another thing: etc folder is used by FileInstall for load of the
configuration, but also by config:update command and config MBeans
to flush a configuration in the etc folder (for instance config:edit
&& config:update creates the config file in the etc folder).

Maybe it makes sense to add the same logic for the  element
of features.

Regards
JB


On 06/24/2013 03:41 PM, Achim Nierbeck wrote:

Hi,

JB told you only half the truth (21) ;)

Configuration Admin service keeps the configuration in Memory that's
correct but it's also stored in the cache folder where the bundle
information is stored.
The etc folder is actually used by the File Installer that scans for
changes and populates the configuration admin service with those.


regards, Achim





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


 Hi Lothar

 it's in memory by default.

  tag in feature only populate ConfigAdmin (memory
only by
 default), and doesn't flush in the etc folder.

 To populate the etc folder, use : it populates
the etc
 folder and load ConfigAdmin using this config file.

 Regards
 JB


 On 06/24/2013 03:30 PM, Lothar Werzinger wrote:

 Hi,

 I created a Karaf feature that contains a configuration
block
 and when I
 install it into Karaf it is properly recognized and
registered
 with the
 given PID. I can however not find where Karaf stores that
 configuration
 information. I assumed that a new file with the
corresponding
 PID will
 be created in the 'etc' folder, but that is clearly not
the case.
 However I can go to the configuration web page of
Karaf, make some
 changes, exit and restart Karaf and the changes are
remembered,
 so they
 are clearly stored somewhere.

 Can you please enlighten me where the configuration
data is stored.

 Oh, and by the way, why does the CA not create a file
in /etc if a
 change is made?
 Because if such a file exists it is updated when a
change is
 made in the
 CA, that's why I assumed the CA would create one if I
provide a
 configuration via a feature.xml as well.

 Thanks in advance!

 P.S.
 I tried the Forum first as instructed on your web site,
but the
 message
 just sits there with a "This post has NOT been accepted
by the
 mailing
 list yet." message, so I am re-posting this message via the
 mailing list.
 --

 Lothar Werzinger

 Principal Architect

 Tradescape, Inc. - Enabling Efficient Digital Marketplaces

 +1-650-931-6719 (direct)

 +1-800-697-6068 (main) Ext. 116

lot...@tradescape.biz 
>






>>


http://www.tradescape.biz




 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 m

Re: How is config admin data stored?

2013-06-24 Thread Achim Nierbeck 
Hi JB,
I think we have a issue for that, and it should be an optional feature :)
https://issues.apache.org/jira/browse/KARAF-545

regards, Achim


2013/6/24 Jean-Baptiste Onofré 

> Thanks Achim, you are right, I forgot to mention the cache folder ;)
>
> Another thing: etc folder is used by FileInstall for load of the
> configuration, but also by config:update command and config MBeans to flush
> a configuration in the etc folder (for instance config:edit &&
> config:update creates the config file in the etc folder).
>
> Maybe it makes sense to add the same logic for the  element of
> features.
>
> Regards
> JB
>
>
> On 06/24/2013 03:41 PM, Achim Nierbeck wrote:
>
>> Hi,
>>
>> JB told you only half the truth (21) ;)
>>
>> Configuration Admin service keeps the configuration in Memory that's
>> correct but it's also stored in the cache folder where the bundle
>> information is stored.
>> The etc folder is actually used by the File Installer that scans for
>> changes and populates the configuration admin service with those.
>>
>>
>> regards, Achim
>>
>>
>>
>>
>>
>> 2013/6/24 Jean-Baptiste Onofré mailto:j...@nanthrax.net>>
>>
>>
>> Hi Lothar
>>
>> it's in memory by default.
>>
>>  tag in feature only populate ConfigAdmin (memory only by
>> default), and doesn't flush in the etc folder.
>>
>> To populate the etc folder, use : it populates the etc
>> folder and load ConfigAdmin using this config file.
>>
>> Regards
>> JB
>>
>>
>> On 06/24/2013 03:30 PM, Lothar Werzinger wrote:
>>
>> Hi,
>>
>> I created a Karaf feature that contains a configuration block
>> and when I
>> install it into Karaf it is properly recognized and registered
>> with the
>> given PID. I can however not find where Karaf stores that
>> configuration
>> information. I assumed that a new file with the corresponding
>> PID will
>> be created in the 'etc' folder, but that is clearly not the case.
>> However I can go to the configuration web page of Karaf, make some
>> changes, exit and restart Karaf and the changes are remembered,
>> so they
>> are clearly stored somewhere.
>>
>> Can you please enlighten me where the configuration data is
>> stored.
>>
>> Oh, and by the way, why does the CA not create a file in /etc if a
>> change is made?
>> Because if such a file exists it is updated when a change is
>> made in the
>> CA, that's why I assumed the CA would create one if I provide a
>> configuration via a feature.xml as well.
>>
>> Thanks in advance!
>>
>> P.S.
>> I tried the Forum first as instructed on your web site, but the
>> message
>> just sits there with a "This post has NOT been accepted by the
>> mailing
>> list yet." message, so I am re-posting this message via the
>> mailing list.
>> --
>>
>> Lothar Werzinger
>>
>> Principal Architect
>>
>> Tradescape, Inc. - Enabling Efficient Digital Marketplaces
>>
>> +1-650-931-6719 (direct)
>>
>> +1-800-697-6068 (main) Ext. 116
>>
>> lot...@tradescape.biz 
>> > lothar@__tradescape.biz
>>
>> > tradescape.biz
>> >>
>>
>>
>> http://www.tradescape.biz
>>
>>
>>
>>
>> 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.
>>
>> -
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org 
>>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
>>
>>
>> --
>>
>> Apache Karaf  Committer & PMC
>> OPS4J Pax Web 
>> >
>> Committer
>> & Project Lead
>> OPS4J Pax for Vaadin 
>> 
>> >
>> Commiter & Project Lead
>> blog 
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.c

Re: How is config admin data stored?

2013-06-24 Thread Jean-Baptiste Onofré 

Thanks Achim, you are right, I forgot to mention the cache folder ;)

Another thing: etc folder is used by FileInstall for load of the 
configuration, but also by config:update command and config MBeans to 
flush a configuration in the etc folder (for instance config:edit && 
config:update creates the config file in the etc folder).


Maybe it makes sense to add the same logic for the  element of 
features.


Regards
JB

On 06/24/2013 03:41 PM, Achim Nierbeck wrote:

Hi,

JB told you only half the truth (21) ;)

Configuration Admin service keeps the configuration in Memory that's
correct but it's also stored in the cache folder where the bundle
information is stored.
The etc folder is actually used by the File Installer that scans for
changes and populates the configuration admin service with those.


regards, Achim





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

Hi Lothar

it's in memory by default.

 tag in feature only populate ConfigAdmin (memory only by
default), and doesn't flush in the etc folder.

To populate the etc folder, use : it populates the etc
folder and load ConfigAdmin using this config file.

Regards
JB


On 06/24/2013 03:30 PM, Lothar Werzinger wrote:

Hi,

I created a Karaf feature that contains a configuration block
and when I
install it into Karaf it is properly recognized and registered
with the
given PID. I can however not find where Karaf stores that
configuration
information. I assumed that a new file with the corresponding
PID will
be created in the 'etc' folder, but that is clearly not the case.
However I can go to the configuration web page of Karaf, make some
changes, exit and restart Karaf and the changes are remembered,
so they
are clearly stored somewhere.

Can you please enlighten me where the configuration data is stored.

Oh, and by the way, why does the CA not create a file in /etc if a
change is made?
Because if such a file exists it is updated when a change is
made in the
CA, that's why I assumed the CA would create one if I provide a
configuration via a feature.xml as well.

Thanks in advance!

P.S.
I tried the Forum first as instructed on your web site, but the
message
just sits there with a "This post has NOT been accepted by the
mailing
list yet." message, so I am re-posting this message via the
mailing list.
--

Lothar Werzinger

Principal Architect

Tradescape, Inc. - Enabling Efficient Digital Marketplaces

+1-650-931-6719 (direct)

+1-800-697-6068 (main) Ext. 116

lot...@tradescape.biz 

>


http://www.tradescape.biz




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.

-


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




--

Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer
& Project Lead
OPS4J Pax for Vaadin 
Commiter & Project Lead
blog 


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

Re: How is config admin data stored?

2013-06-24 Thread Achim Nierbeck 
Hi,

JB told you only half the truth (21) ;)

Configuration Admin service keeps the configuration in Memory that's
correct but it's also stored in the cache folder where the bundle
information is stored.
The etc folder is actually used by the File Installer that scans for
changes and populates the configuration admin service with those.


regards, Achim





2013/6/24 Jean-Baptiste Onofré 

> Hi Lothar
>
> it's in memory by default.
>
>  tag in feature only populate ConfigAdmin (memory only by
> default), and doesn't flush in the etc folder.
>
> To populate the etc folder, use : it populates the etc folder
> and load ConfigAdmin using this config file.
>
> Regards
> JB
>
>
> On 06/24/2013 03:30 PM, Lothar Werzinger wrote:
>
>> Hi,
>>
>> I created a Karaf feature that contains a configuration block and when I
>> install it into Karaf it is properly recognized and registered with the
>> given PID. I can however not find where Karaf stores that configuration
>> information. I assumed that a new file with the corresponding PID will
>> be created in the 'etc' folder, but that is clearly not the case.
>> However I can go to the configuration web page of Karaf, make some
>> changes, exit and restart Karaf and the changes are remembered, so they
>> are clearly stored somewhere.
>>
>> Can you please enlighten me where the configuration data is stored.
>>
>> Oh, and by the way, why does the CA not create a file in /etc if a
>> change is made?
>> Because if such a file exists it is updated when a change is made in the
>> CA, that's why I assumed the CA would create one if I provide a
>> configuration via a feature.xml as well.
>>
>> Thanks in advance!
>>
>> P.S.
>> I tried the Forum first as instructed on your web site, but the message
>> just sits there with a "This post has NOT been accepted by the mailing
>> list yet." message, so I am re-posting this message via the mailing list.
>> --
>>
>> Lothar Werzinger
>>
>> Principal Architect
>>
>> Tradescape, Inc. - Enabling Efficient Digital Marketplaces
>>
>> +1-650-931-6719 (direct)
>>
>> +1-800-697-6068 (main) Ext. 116
>>
>> lot...@tradescape.biz
>> > tradescape.biz
>> >
>>
>>
>> http://www.tradescape.biz
>>
>>
>>
>>
>> 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.
>>
>> -
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>



-- 

Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
OPS4J Pax for Vaadin 
Commiter & Project Lead
blog

Re: How is config admin data stored?

2013-06-24 Thread Jean-Baptiste Onofré 

Hi Lothar

it's in memory by default.

 tag in feature only populate ConfigAdmin (memory only by 
default), and doesn't flush in the etc folder.


To populate the etc folder, use : it populates the etc 
folder and load ConfigAdmin using this config file.


Regards
JB

On 06/24/2013 03:30 PM, Lothar Werzinger wrote:

Hi,

I created a Karaf feature that contains a configuration block and when I
install it into Karaf it is properly recognized and registered with the
given PID. I can however not find where Karaf stores that configuration
information. I assumed that a new file with the corresponding PID will
be created in the 'etc' folder, but that is clearly not the case.
However I can go to the configuration web page of Karaf, make some
changes, exit and restart Karaf and the changes are remembered, so they
are clearly stored somewhere.

Can you please enlighten me where the configuration data is stored.

Oh, and by the way, why does the CA not create a file in /etc if a
change is made?
Because if such a file exists it is updated when a change is made in the
CA, that's why I assumed the CA would create one if I provide a
configuration via a feature.xml as well.

Thanks in advance!

P.S.
I tried the Forum first as instructed on your web site, but the message
just sits there with a "This post has NOT been accepted by the mailing
list yet." message, so I am re-posting this message via the mailing list.
--

Lothar Werzinger

Principal Architect

Tradescape, Inc. - Enabling Efficient Digital Marketplaces

+1-650-931-6719 (direct)

+1-800-697-6068 (main) Ext. 116

lot...@tradescape.biz


http://www.tradescape.biz




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.

-



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