While I’m used to both Eclipse and Java, OSGi is new to me - and this far the logic obviously hasn’t snuck into my brain - resulting in feeling pretty helpless when things don’t work.
I’m at the very beginning of trying to develop a new binding. I’ve done some modifications to the “skeleton binding”, but nothing really significant yet. This behavior was also there when the “skeleton binding” was unmodified.
When I add a new thing, my binding code is called and everything seems to work. But once I have restarted the “demo app”, the previously created things are UNINITIALIZED and NOT_YET_READY. If I try to delete them, they get stuck in REMOVING instead.
While I don’t know if the underlying cause is the same, the sympoms are very similar to those discussed here:
The suggested workarounds I find don’t help me, because I understand so little of the OSGi environment. I don’t know “where it runs”, so I have no idea where to create folders as a workaround. In the “demo app”, under runtime, there is a conf/items folder, where some demo items live. But, that’s apparently not sufficient. Likewise, running things like bundle:restart 200 doesn’t tell me anything, since I don’t seem to have a “karaf” console to run commands from.
Until now I’ve just added a new thing for each debug session, but the list is growing and I have to configure it each time - it’s not a viable approach. Can anyone help me figure out how to get around this?
It seems that this bug has been around for a while, I’d really wish someone with the required knowledge would fix it, as issues like this are stumbling blocks for new contributors that can easily make people give up.
