| Summary: | Web application bundle cannot be resolved when osgi.resolverMode is in strict mode | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] Gemini.Web | Reporter: | Violeta Georgieva <milesg78> | ||||
| Component: | unknown | Assignee: | Violeta Georgieva <milesg78> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | glyn.normington | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 2.0.0.M02 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Violeta Georgieva
When the "osgi.resolverMode" is set to "strict" we have the following requirement: "strict - the resolver is in strict mode and will enforce access restriction rules when loading classes and resources from exported packages which specify the x-internal or x-friends directives." When generating the web application manifest, we are adding to its export packages, all system bundle exports. We are using PackageAdmin for this purpose and it appears that we add also the system bundle exports that have x-internal or x-friends directives. This is the cause for the failure. org.eclipse.gemini.web.internal.SystemBundleExportsResolver is the class that is responsible for resolving system bundle export packages. Instead of PackageAdmin, I'm using now the new API - BundleWiring and BundleCapability. I'm attaching a patch for this bug. Can you please review it and comment on it. Thanks Vily Created attachment 198165 [details]
Patch proposal
Comment on attachment 198165 [details]
Patch proposal
Looks good.
Thanks Change committed, tested and pushed. |