Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [osgi-users] Fwd: Dynamic component behavior


On Mon, Jul 5, 2021 at 12:15 PM Dirk Fauth via osgi-users <osgi-users@xxxxxxxxxxx> wrote:

Well, I wanted to switch to dynamic services and had been using greedy before but looking at the example here I lost that part, while having the referenced page open at the same time.

So that resolves this issue, thanks Dirk, but still leaves me with the 2nd one, where the service fails to load most of the time (restarting a few times and I will finally find a run that works).

In the same realm and with the same component, I'm facing another issue. And please note that this is not new code but just now called earlier in the startup process.

Here I have a service tracker used to get my service reference for the ActivatorComponents shown in my previous email.

Listing services from the console and matching all references or using our internal tool returns:
osgi> checkRefs com.castortech.iris.emf.irisdb.custom.activator.ActivatorComponents
Checking for com.castortech.iris.emf.irisdb.custom.activator.ActivatorComponents references
  Referenced service com.castortech.iris.emf.irisdb.custom.api.BaTypeUtils/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.CoreAttributeUtils/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.CoreClassUtils/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.CoreInstanceUtils/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.CoreModelHelper/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.CoreOptFeatureUtils/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.CoreRelationshipUtils/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.CoreStereotypeHelper/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.CoreStereotypeUtils/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.CoreTypeUtils/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.CoreUtils/dynamic is registered
  Referenced service com.castortech.iris.utils.eclipse.iemf.custom.GenericExpressionResolver/dynamic is registered
  Referenced service com.castortech.util.html.IHtmlService/dynamic is registered
  Referenced service com.castortech.iris.image.IrisImage/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.NotificationHelper/dynamic is registered
  Referenced service com.castortech.iris.emf.irisdb.custom.api.TimestampableElementUtils/optional,dynamic is registered

indicating that all dependent referenced services are registered and ready to go. Why wouldn't the service tracker return a service reference for it? BTW, we use a retry process that is tested a number of times over about 5 secs, just to make sure that things get resolved. I have never seen this before.

Back to the top