Hi there, I’ve just found a scenario where one of our Micro Services is registered twice and I’m debugging whats going on.
However, in this documentation: http://docs.mitk.org/nightly/MicroServices_Overview.html http://docs.mitk.org/nightly/MicroServices_Example2.html the us::ModuleActivator has Load/Unload methods. The Load basically calls context->RegisterService, and the Unload method says the service is automatically unloaded. This is what our service was modelled on. However in this example, a ServiceTracker is used: http://docs.mitk.org/nightly/MicroServices_Example7.html And in this example, there is a ServiceRegistration and a ServiceTracker: http://docs.mitk.org/nightly/MicroServices_Example6.html I also notice that in services like the PersistenceService and PythonService, the Service and ServiceRegistration are both Unregistered/Deleted manually in the Unload method. So whats the correct or preferred approach? I just have a Module that should register a MicroService when it is loaded, and unregister a MicroService when it is unloaded. It also seems to me that I have to manually delete things in the unload method. Is that right? We have quite a few MicroServices, that Im now worrything that I need to go and change. Thanks Matt
------------------------------------------------------------------------------
_______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users