WRT - https://github.com/apache/camel-karaf/blob/main/features/src/main/feature/camel-features.xml#L165
feature named "xml-specs-api" has defined start-level of bundles as 10 but only bundles listed inside "xml-specs-api" are started at that level and the features and their respective bundles do not start at level 10 because the features listed inside "xml-specs-api" does not list any start up level hence the bundles of those features start at default start-level of karaf which is 80.
bundles which start at level 10 -
https://github.com/apache/camel-karaf/blob/main/features/src/main/feature/camel-features.xml#L174-L175
bundles of feature used inside "xml-specs-api" does not start at level 10 as there is no start-level defined in their features -
https://github.com/apache/camel-karaf/blob/main/features/src/main/feature/camel-features.xml#L166-L173
E.g. - feature "jakarta-activation" and bundle jakarta.activation-api will start at karaf default start-level which is 80.
https://github.com/apache/camel-karaf/blob/main/features/src/main/feature/camel-features.xml#L25-L26
Why this is a problem ? Or Could be a problem ?
Mostly camel features have start-level 50, if we indent to run some custom user bundle at start-level lets say 60, the dependent/required xml bundles will fail with ClassNotFound exception or something else as they will be started at karaf default start-level 80.
So should we start all features used inside "xml-specs-api" at start-level 10 too ?
WRT - https://github.com/apache/camel-karaf/blob/main/features/src/main/feature/camel-features.xml#L165
feature named "xml-specs-api" has defined start-level of bundles as 10 but only bundles listed inside "xml-specs-api" are started at that level and the features and their respective bundles do not start at level 10 because the features listed inside "xml-specs-api" does not list any start up level hence the bundles of those features start at default start-level of karaf which is 80.
bundles which start at level 10 -
https://github.com/apache/camel-karaf/blob/main/features/src/main/feature/camel-features.xml#L174-L175
bundles of feature used inside "xml-specs-api" does not start at level 10 as there is no start-level defined in their features -
https://github.com/apache/camel-karaf/blob/main/features/src/main/feature/camel-features.xml#L166-L173
E.g. - feature "jakarta-activation" and bundle jakarta.activation-api will start at karaf default start-level which is 80.
https://github.com/apache/camel-karaf/blob/main/features/src/main/feature/camel-features.xml#L25-L26
Why this is a problem ? Or Could be a problem ?
Mostly camel features have start-level 50, if we indent to run some custom user bundle at start-level lets say 60, the dependent/required xml bundles will fail with ClassNotFound exception or something else as they will be started at karaf default start-level 80.
So should we start all features used inside "xml-specs-api" at start-level 10 too ?