Thanks,
I'll be watching the issue. Meanwhile do you have any idea how to work
around it?
Regards,
Milen
On Mon, Sep 1, 2014 at 7:21 AM, Clement Escoffier <
clement.escoff...@gmail.com> wrote:
> Hi,
>
> It seems that the bug is back. I’ve re-opened the issue.
>
> Thanks,
>
> Clement
>
> On 31 août 2014 at 12:24:49, Milen Dyankov (milendyan...@gmail.com) wrote:
>
> Hi everyone,
>
> I'm aware this issue has been reported (FELIX-4172) and apparently fixed in
> ipojo-runtime-1.11.0. However the same (or very similar one) happens in
> Karaf 3.0.1 with IPojo 1.12.0.
>
> Here is my very simple test class:
>
> @Component(
> immediate = true,
> managedservice = "update.test")
> @Provides
> @Instantiate
> public class UpdateTest implements TestInterface {
>
> @Override
> public void test() {
> }
>
> @Updated
> public void update(Dictionary dictionary) {
> Thread t = Thread.currentThread();
> System.out.println();
> System.out.println("PROPERTIES UPDATED \n" +
> " in thread: [" + t.getName() + "] \n" +
> " values: " + dictionary);
> }
>
> }
>
> In Karaf I have a simple "update.test.cfg" file containing "
> test.property=test.value"!
>
> When I deploy my bundle in Karaf this is what I get:
>
> PROPERTIES UPDATED
> in thread: [[iPOJO] pool-1-thread-1]
> values: {test.property=test.value, component=test.UpdateTest,
>
> felix.fileinstall.filename=file:/data/projects/tmp/karaf/apache-karaf-3.0.1/etc/update.test.cfg}
> PROPERTIES UPDATED
> in thread: [CM Configuration Updater (ManagedService Update:
> pid=[update.test])]
> values: {test.property=test.value, component=test.UpdateTest,
>
> felix.fileinstall.filename=file:/data/projects/tmp/karaf/apache-karaf-3.0.1/etc/update.test.cfg}
>
>
> Is this a bug?
>
> --
> http://about.me/milen
>
--
http://about.me/milen
