A developer is creating a new OSGi bundle com.custom.package.b to expose new services. com.custom.package.a is already installed and active in the system and has the following package definition:
The system console shows the following package availability:
Bundle com.custom.package.b to be installed has the following package definition:
What will happen when the developer uploads the bundle com.custom.package.b into the system?
The bundle com.custom.package.b will install but fail the activation due to unsatisfied dependency com.sample.package.b. Reviewing the information, com.custom.package.b requires com.sample.package.b;version="[3.0,3.0]" which means it needs exactly version 3.0. However, there is no com.sample.package.b in the list of available packages in the system console. Therefore, this dependency cannot be satisfied, leading to a failure in activation.
Ans B, package.b cannot import package.c due to its version
Isn't D ?
A is the most suitable answer, but it is not complete – it should also include an unsatisfied dependency to com.custom.package.a, because the specified version range [1,2) does not allow version 2.0 to be imported.
It seems All are the wrong answers here. The correct answer should be: fail the activation due to unsatisfied dependencies com.sample.package.a and com.sample.package.c.