You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by "Leschke, Scott" <SL...@medline.com> on 2016/09/09 14:20:46 UTC
Component configuration pid
I have a component on which I've changed the configuration pid. I made the change and redeployed the bundle in which it resides. The pid doesn't get updated though (as shown by scr:info). How do I go about getting the pid to update? I see no provision in SCR for deleting or refreshing the component in some way.
Scott
Re: Component configuration pid
Posted by David Jencks <da...@gmail.com>.
> On Sep 9, 2016, at 11:00 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> I fixed that already and you can use the felix command.
>
Thank you!
david jencks
> Regards
> JB
>
> On 09/10/2016 05:50 AM, David Jencks wrote:
>>
>>> On Sep 9, 2016, at 8:07 PM, Benson Margulies <benson@basistech.com
>>> <ma...@basistech.com>> wrote:
>>>
>>>
>>>
>>> On Fri, Sep 9, 2016 at 10:00 PM, David Jencks
>>> <david.a.jencks@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Well, either
>>> 1. you didn’t actually succeed in creating a bundle with a
>>> different pid for your component. Look in the (I hope generated)
>>> xml configuration in the bundle you’ve created and see if it’s
>>> what you expect.
>>> 2. you didn’t actually succeed in deploying your updated bundle.
>>> If your new bundle has a different version than the old one you
>>> should be able to distinguish which one is actually activated.
>>> 3. karaf’s scr:info is flakier than I think possible.
>>>
>>> I really don’t think (3) is plausible.
>>>
>>>
>>> At least in 4.0.4, the Karaf scr:info command is very confusing. The
>>> Felix command scr:details that comes along with scr itself is much
>>> more informative. I am not, however, prepared to contradict your view.
>>
>> I’ve heard about that and don’t understand why they don’t just use the
>> felix one or if something’s missing from it file a bug in felix.
>> However I find it hard to believe it could report the pid(s) wrong.
>>
>> thanks
>> david jencks
>>
>>>
>>> david jencks
>>>
>>>> On Sep 9, 2016, at 7:20 AM, Leschke, Scott <SLeschke@medline.com
>>>> <ma...@medline.com>> wrote:
>>>>
>>>> I have a component on which I’ve changed the configuration pid. I
>>>> made the change and redeployed the bundle in which it resides.
>>>> The pid doesn’t get updated though (as shown by scr:info). How
>>>> do I go about getting the pid to update? I see no provision in
>>>> SCR for deleting or refreshing the component in some way.____
>>>> __ __
>>>> Scott
>>>
>>>
>>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
Re: Component configuration pid
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I fixed that already and you can use the felix command.
Regards
JB
On 09/10/2016 05:50 AM, David Jencks wrote:
>
>> On Sep 9, 2016, at 8:07 PM, Benson Margulies <benson@basistech.com
>> <ma...@basistech.com>> wrote:
>>
>>
>>
>> On Fri, Sep 9, 2016 at 10:00 PM, David Jencks
>> <david.a.jencks@gmail.com <ma...@gmail.com>> wrote:
>>
>> Well, either
>> 1. you didn\u2019t actually succeed in creating a bundle with a
>> different pid for your component. Look in the (I hope generated)
>> xml configuration in the bundle you\u2019ve created and see if it\u2019s
>> what you expect.
>> 2. you didn\u2019t actually succeed in deploying your updated bundle.
>> If your new bundle has a different version than the old one you
>> should be able to distinguish which one is actually activated.
>> 3. karaf\u2019s scr:info is flakier than I think possible.
>>
>> I really don\u2019t think (3) is plausible.
>>
>>
>> At least in 4.0.4, the Karaf scr:info command is very confusing. The
>> Felix command scr:details that comes along with scr itself is much
>> more informative. I am not, however, prepared to contradict your view.
>
> I\u2019ve heard about that and don\u2019t understand why they don\u2019t just use the
> felix one or if something\u2019s missing from it file a bug in felix.
> However I find it hard to believe it could report the pid(s) wrong.
>
> thanks
> david jencks
>
>>
>> david jencks
>>
>>> On Sep 9, 2016, at 7:20 AM, Leschke, Scott <SLeschke@medline.com
>>> <ma...@medline.com>> wrote:
>>>
>>> I have a component on which I\u2019ve changed the configuration pid. I
>>> made the change and redeployed the bundle in which it resides.
>>> The pid doesn\u2019t get updated though (as shown by scr:info). How
>>> do I go about getting the pid to update? I see no provision in
>>> SCR for deleting or refreshing the component in some way.____
>>> __ __
>>> Scott
>>
>>
>
--
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Component configuration pid
Posted by David Jencks <da...@gmail.com>.
> On Sep 9, 2016, at 8:07 PM, Benson Margulies <be...@basistech.com> wrote:
>
>
>
> On Fri, Sep 9, 2016 at 10:00 PM, David Jencks <david.a.jencks@gmail.com <ma...@gmail.com>> wrote:
> Well, either
> 1. you didn’t actually succeed in creating a bundle with a different pid for your component. Look in the (I hope generated) xml configuration in the bundle you’ve created and see if it’s what you expect.
> 2. you didn’t actually succeed in deploying your updated bundle. If your new bundle has a different version than the old one you should be able to distinguish which one is actually activated.
> 3. karaf’s scr:info is flakier than I think possible.
>
> I really don’t think (3) is plausible.
>
> At least in 4.0.4, the Karaf scr:info command is very confusing. The Felix command scr:details that comes along with scr itself is much more informative. I am not, however, prepared to contradict your view.
I’ve heard about that and don’t understand why they don’t just use the felix one or if something’s missing from it file a bug in felix. However I find it hard to believe it could report the pid(s) wrong.
thanks
david jencks
>
> david jencks
>
>> On Sep 9, 2016, at 7:20 AM, Leschke, Scott <SLeschke@medline.com <ma...@medline.com>> wrote:
>>
>> I have a component on which I’ve changed the configuration pid. I made the change and redeployed the bundle in which it resides. The pid doesn’t get updated though (as shown by scr:info). How do I go about getting the pid to update? I see no provision in SCR for deleting or refreshing the component in some way.
>>
>> Scott
>
>
Re: Component configuration pid
Posted by Benson Margulies <be...@basistech.com>.
On Fri, Sep 9, 2016 at 10:00 PM, David Jencks <da...@gmail.com>
wrote:
> Well, either
> 1. you didn’t actually succeed in creating a bundle with a different pid
> for your component. Look in the (I hope generated) xml configuration in
> the bundle you’ve created and see if it’s what you expect.
> 2. you didn’t actually succeed in deploying your updated bundle. If your
> new bundle has a different version than the old one you should be able to
> distinguish which one is actually activated.
> 3. karaf’s scr:info is flakier than I think possible.
>
> I really don’t think (3) is plausible.
>
At least in 4.0.4, the Karaf scr:info command is very confusing. The Felix
command scr:details that comes along with scr itself is much more
informative. I am not, however, prepared to contradict your view.
>
> david jencks
>
> On Sep 9, 2016, at 7:20 AM, Leschke, Scott <SL...@medline.com> wrote:
>
> I have a component on which I’ve changed the configuration pid. I made the
> change and redeployed the bundle in which it resides. The pid doesn’t get
> updated though (as shown by scr:info). How do I go about getting the pid
> to update? I see no provision in SCR for deleting or refreshing the
> component in some way.
>
> Scott
>
>
>
Re: Component configuration pid
Posted by David Jencks <da...@gmail.com>.
Well, either
1. you didn’t actually succeed in creating a bundle with a different pid for your component. Look in the (I hope generated) xml configuration in the bundle you’ve created and see if it’s what you expect.
2. you didn’t actually succeed in deploying your updated bundle. If your new bundle has a different version than the old one you should be able to distinguish which one is actually activated.
3. karaf’s scr:info is flakier than I think possible.
I really don’t think (3) is plausible.
david jencks
> On Sep 9, 2016, at 7:20 AM, Leschke, Scott <SL...@medline.com> wrote:
>
> I have a component on which I’ve changed the configuration pid. I made the change and redeployed the bundle in which it resides. The pid doesn’t get updated though (as shown by scr:info). How do I go about getting the pid to update? I see no provision in SCR for deleting or refreshing the component in some way.
>
> Scott