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 <[email protected]
<mailto:[email protected]>> wrote:
On Fri, Sep 9, 2016 at 10:00 PM, David Jencks
<[email protected] <mailto:[email protected]>> 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 <[email protected]
<mailto:[email protected]>> 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é
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
