Details

    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.0
    • Component/s: kernel, osgi
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      currently when we deploy an ee app we add import-packages for the geronimo bits needed for the gbeans to run it to the resulting plugin's manifest.mf. This has a couple of undesirable features:

      1. the geronimo classes are visible to the app.
      2. we can't use our deployment for things like osgi rfc 66 which start with a bundle that happens to be a WAB and doesn't allow for modifying the manifest to add our import-packages. We could possibly work around this by using fragment bundles associated with the WAB but this still alters the visibility environment of the app.

      Proposed solution is to add a field

      private Artifact classSource

      to GBeanData that a module builder can set to indicate to GBeanInstance where the class should be loaded from. This is quite gbean-centric in that we are using geronimo artifacts to identify a geronimo plugin rather than something more osgi-friendly. However, since we're using gbeans, this might not be such a big problem.

        Activity

          People

          • Assignee:
            David Jencks
            Reporter:
            David Jencks
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development