Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0.0
-
Security Level: public (Regular issues)
-
None
Description
Right now we are generating "nested bundles" inside plugins for ear files with web modules. These don't quite work. One code problem is that the SimpleConifgurationManager tries to start the child bundles before the configuration for the parent/containing bundle is registered, so a getConfiguration call to find the parent config fails. This is probably easy to fix.
However a bigger issue is that there's no way to tell the osgi framework about the nested bundle. Three possible solutions:
1. stop having nested bundles, just use one bundle per ear. This is a 1-line change in AbstractWebModuleBuilder so I expect to use this until we can actually solve the problem
2. modify the pax mvn url handler to deal with urls to nested bundles inside the car.
3. modify the ear deployer to create more than one bundle from an ear.