You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by João Assunção <jo...@joaoassuncao.com> on 2008/09/22 16:46:10 UTC

Strange behavior in managed iPOJO

Hello,

I created a managed iPOJO with some instance properties defined in the
metadata descriptor with default values. I was expecting to find a
Configuration associated to the managed.service.pid, but there wasn't one
available.
Using the ConfigurationAdmin service  I created a Configuration for my
iPOJO, and I was able to change some properties. But when I restart the
bundle, the iPOJO instance is using the values defined in the metadata
descriptor instead of the ones present in the Configuration. I get a debug
message saying that the Configuration for my managed.service.pid has already
been delivered.
I find this behavior strange (at least for me) and I'd like to know if this
is normal.

Thanks.
Joao

RE: Strange behavior in managed iPOJO

Posted by Clement Escoffier <cl...@gmail.com>.
Hello,

I was not able to reproduce the bug, but as I solve another issue with the
configuration admin, it should solve this one too. Ping me if you see the
bug again.

Clement

-----Original Message-----
From: João Assunção <jo...@joaoassuncao.com> [mailto:=?ISO-8859-1?Q?
Jo=E3o_Assun=E7=E3o _<jo...@joaoassuncao.com>?=] 
Sent: lundi 22 septembre 2008 16:46
To: users@felix.apache.org
Subject: Strange behavior in managed iPOJO

Hello,

I created a managed iPOJO with some instance properties defined in the
metadata descriptor with default values. I was expecting to find a
Configuration associated to the managed.service.pid, but there wasn't one
available.
Using the ConfigurationAdmin service  I created a Configuration for my
iPOJO, and I was able to change some properties. But when I restart the
bundle, the iPOJO instance is using the values defined in the metadata
descriptor instead of the ones present in the Configuration. I get a debug
message saying that the Configuration for my managed.service.pid has already
been delivered.
I find this behavior strange (at least for me) and I'd like to know if this
is normal.

Thanks.
Joao


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: Strange behavior in managed iPOJO

Posted by clement escoffier <cl...@gmail.com>.
Hi,

For sure it's a strange behavior.
It sounds like a bug. Could you open a Jira issue (
https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12312610)
with your configuration (the metadata.xml file and the version of the
configuration admin). I will recreate the bug to  solve it.

Thank you very much

Regards,

Clement

2008/9/22 João Assunção <jo...@joaoassuncao.com>

> Hello,
>
> I created a managed iPOJO with some instance properties defined in the
> metadata descriptor with default values. I was expecting to find a
> Configuration associated to the managed.service.pid, but there wasn't one
> available.
> Using the ConfigurationAdmin service  I created a Configuration for my
> iPOJO, and I was able to change some properties. But when I restart the
> bundle, the iPOJO instance is using the values defined in the metadata
> descriptor instead of the ones present in the Configuration. I get a debug
> message saying that the Configuration for my managed.service.pid has
> already
> been delivered.
> I find this behavior strange (at least for me) and I'd like to know if this
> is normal.
>
> Thanks.
> Joao
>