Freeman Fang commented on KARAF-3513:

Hi Paolo,

The fix for KARAF-3515 on master is [1].

In Karaf 4.x we get rid of the compulsory blueprint dependency so in Karaf 4.x 
this fix introduce a ServiceTracker in Activator which play the same role as 
reference-listener bind/unbind method in blueprint configuration of Karaf 
2.x/3.x to handle the service come and go dynamically.

So about your patch on karaf master, I think you can merge your 
register/unregister logic in the ServiceTracker of Activator, in the 
addingService/removedService separately.



> JMXConnectorServer should be able to pick up the new KeystoreInstance 
> available in container
> --------------------------------------------------------------------------------------------
>                 Key: KARAF-3513
>                 URL: https://issues.apache.org/jira/browse/KARAF-3513
>             Project: Karaf
>          Issue Type: Improvement
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 2.4.2, 3.0.4, 4.0.0.M3
> when we configure the JMX Connector with SSL enabled, if there's no valid 
> keystore available in the first place when start the  "Apache Karaf :: 
> Management" bundle,  that bundle can't pick up any KeystoreInstance available 
> afterwards.
> For an instance, if we drop a keystore.xml file like
> {code}
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";
>           xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0";>
>     <jaas:keystore name="sample_keystore"
>                    rank="1"
>                    path="..."
>                    keystorePassword="..."
>                    keyPasswords="..." />
> </blueprint>
> {code}
> into etc folder after we start karaf, a bundle created accordingly and a 
> KeystoreInstance get published, however, the JMX Connector  won't be able to 
> pick up this new KeystoreInstance, unless we manually refresh "Apache Karaf 
> :: Management" bundle.

This message was sent by Atlassian JIRA

Reply via email to