Class Platform

    • Field Detail

      • context

        protected org.osgi.framework.BundleContext context
    • Constructor Detail

      • Platform

        public Platform()
    • Method Detail

      • start

        public void start​(org.osgi.framework.BundleContext context)
      • stop

        public void stop​(org.osgi.framework.BundleContext context)
      • moduleStarted

        public void moduleStarted​(long moduleId)
        There are two scenarios when this event callback is being called: when a module is INSTALLED and when a module is UPDATED. Install: - moduleInstalled: state=INSTALLED - moduleStarted: state=STARTED Update (e.g. because component source code was changed - no hot-swap -): - moduleStopping: state=RESOLVED - componentUnregistering: state=UNRESOLVED - moduleStopped: state=UNRESOLVED (no-op) - componentRegistered: state=STARTED (auto-start when all components are resolved) - moduleStarted: state=STARTED (no-op)
        Specified by:
        moduleStarted in interface EventListener
      • moduleStopped

        public void moduleStopped​(long moduleId)
        When the OSGi container process is stopped, 'moduleStopping' is not called therefore the module is still registered in the ModuleManager. 'moduleStopped' is called when the OSGi container shuts down (skipping the call to moduleStopping). Note that when a module is stopped there is no more context (Bundle Context) associated with it.
        Specified by:
        moduleStopped in interface EventListener