Details

      Description

      This issue is described in section 3.15 of the OSGi R4 specification. The main jist is to provide a standard mechanism to place classes on the JVM boot class path and to deliver framework extensions and/or updates. This mechanisms is modeled as bundle fragments, but it not really completely related to it. The boot class path aspect is likely to be dependent on specific JVMs.

        Activity

        Hide
        Karl Pauls added a comment -

        As of Revision 506755 the extension:=framework part of the spec is implemented with the exception of automatic framework restart on extension bundle refresh.

        Show
        Karl Pauls added a comment - As of Revision 506755 the extension:=framework part of the spec is implemented with the exception of automatic framework restart on extension bundle refresh.
        Hide
        Karl Pauls added a comment -

        The extension:= framework part of the spec was broken for some time. It should be working again as of revision 576163.

        Show
        Karl Pauls added a comment - The extension:= framework part of the spec was broken for some time. It should be working again as of revision 576163.
        Hide
        Karl Pauls added a comment - - edited

        We have support for framework extension bundles since a long time now. I think we should close this issue and create a new one for bootclasspath extension bundles.

        Show
        Karl Pauls added a comment - - edited We have support for framework extension bundles since a long time now. I think we should close this issue and create a new one for bootclasspath extension bundles.

          People

          • Assignee:
            Karl Pauls
            Reporter:
            Richard S. Hall
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development