Details

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

      Description

      Currently the osgi framework only works with plugins packed as jar files, not exploded jar files like the regular geronimo server. Since osgi can deal with classpaths inside a jar file, I rather think that we should proceed with this as standard practice for the rest of the server. However this will mean moving the archiving functionality out of the car-maven-plugin and into the deployer.

      The alternative is to make sure that unpacked plugins actually work in osgi. I didn't experiment with this at all.

        Activity

        Hide
        David Jencks added a comment -

        I haven't heard of problems recently so think this is working ok.

        Show
        David Jencks added a comment - I haven't heard of problems recently so think this is working ok.
        Hide
        David Jencks added a comment -

        I would really rather not unpack plugins unless we have no alternative, so I'll look into fixing these problems.

        Show
        David Jencks added a comment - I would really rather not unpack plugins unless we have no alternative, so I'll look into fixing these problems.
        Hide
        Shawn Jiang added a comment -

        Currently, some API that assumes car are exploded are not working well because car are packed in Geronimo 3.0. Some of them are:

        RepositoryConfigurationStore.listConfigurations()
        ExecutableConfigurationUtil.writeConfiguration(ConfigurationData, File)
        RepositoryConfigurationStore.createNewConfigurationDir(Artifact)

        Which are keeping me from migrating some of deployer shell commands.

        Show
        Shawn Jiang added a comment - Currently, some API that assumes car are exploded are not working well because car are packed in Geronimo 3.0. Some of them are: RepositoryConfigurationStore.listConfigurations() ExecutableConfigurationUtil.writeConfiguration(ConfigurationData, File) RepositoryConfigurationStore.createNewConfigurationDir(Artifact) Which are keeping me from migrating some of deployer shell commands.
        Hide
        Shawn Jiang added a comment -

        Seems karaf support exploded bundles already, See: http://felix.apache.org/site/1-overview.html

        In addition, the Karaf also supports exploded bundles and custom deployers (blueprint and spring ones are included by default).

        Show
        Shawn Jiang added a comment - Seems karaf support exploded bundles already, See: http://felix.apache.org/site/1-overview.html In addition, the Karaf also supports exploded bundles and custom deployers (blueprint and spring ones are included by default).
        Hide
        Rick McGuire added a comment -

        There was some recent discussion within osgi of defining a standard URL handler to allow a directory of files to be loaded as a bundle. There was a lot of discussion, but I'm not sure it really went anywhere. I'm not aware that there's any standard ability to do this.

        Show
        Rick McGuire added a comment - There was some recent discussion within osgi of defining a standard URL handler to allow a directory of files to be loaded as a bundle. There was a lot of discussion, but I'm not sure it really went anywhere. I'm not aware that there's any standard ability to do this.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development