Community
Participate
Working Groups
Loading Update state on startup (if nothing has changed i.e. no reconciliation has to be performed) takes time that is proportional to the number of features saved. Investigate if we need all the state information right away: 1) We may not need all the histories loaded right away. We can create the configuration object but delay parsing the file until this object is actually needed i.e. until 'getConfiguredSites' is called on the IInstallConfiguration object in history. 2) The same for saved configurations. 3) Investigate parser code and see if there are bottlenecks
Action Taken: we may add a new label attribute in the feature tag of site.xml. This will prevent from downloading the features until other attributes are needed. If the site parser finds a label attribute in site.xml it will set it into feature reference and use it, otherwise feature reference will delegate the call to the feature. Action Plan: implement core , update spec and implement UI to call IFeatureReference.getLabel()
I beleive we have a 'name' attribute in the IIncludedFeatureReference (includes element), so we may use the same here to be consistent.
Wrong bug, comments should have been in bug 26943
Action Taken: bug 27051 contains the fix this issue Action Plan: wait for bug 27051
done.
