Sorting module's startlevel defined in subsystem xml file to start subsystem #15

Closed
tangyong opened this Issue Jan 30, 2013 · 3 comments

Comments

Projects
None yet
1 participant
Owner

tangyong commented Jan 30, 2013

Once starting modules defined in subsystem xml file, we must firstly sort module's startlevel defined in subsystem xml file if setting startlevel.

@ghost ghost assigned tangyong Jan 30, 2013

Owner

tangyong commented Jan 30, 2013

Currently, there is an issue needing to confirm with sahoo, in ObrHandlerServiceImpl class, there is a bool flag called deployOptionalRequirements, which comes from previous osgi-adapter module's obrhandler class. Because of the flag, while felix obr resolver is executing deploy(flag), it will start installed bundles if the flag is true. So, if using subsystem to provisioning, because whether to start the module has been defined in xml file, we should start the corresponding module based on start and startlevel attributes rather than deployOptionalRequirements.

So, needing to discuss with sahoo in depth.

Owner

tangyong commented Jan 30, 2013

  1. adding some apis into ObrHandlerService as following:

public void deploySubsystems(String subSystemPath, boolean start);

public void deploySubsystem(String subSystemPath, String subSystemName, boolean start);

if not specifying start parameter, currently, we consider the case to start subsystem

  1. adding module starting logic based on module's startlevel and start attributes

tangyong pushed a commit that referenced this issue Jan 30, 2013

tangyong
#15 adding some apis into ObrHandlerService and module starting logi…
…c based on module startlevel and start attributes
Owner

tangyong commented Jan 31, 2013

Done.

@tangyong tangyong closed this Jan 31, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment