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