Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.0.1
    • Component/s: general
    • Labels:
      None

      Description

      Geronimo needs pluto to come with more osgi support. We don't know yet exactly what this will entail. Some possible bits:

      1. make the jars into osgi bundles. This should be completely non-controversial and easy.
      2. use the osgi blueprint service instead of spring. This could be an optional other way of assembling the portal (most likely) or a replacement (I doubt this would be acceptable to everyone at this point).
      3. Investigate deploying the wars as rfc 66 web app bundles. I'm not sure whether or not this would be useful for geronimo.

        Activity

        Hide
        Ate Douma added a comment -

        Seems to me nobody encountered any problems with this so far, qualifying this as fixed to me.

        Show
        Ate Douma added a comment - Seems to me nobody encountered any problems with this so far, qualifying this as fixed to me.
        Hide
        David Jencks added a comment -

        rev 893689 is a fairly substantial refactoring to use more DI. This works in geronimo assembled using blueprint, but I don't have a good way to test the spring assembly, which may well not work properly.

        Please let me know of problems and I will work to fix them.

        Show
        David Jencks added a comment - rev 893689 is a fairly substantial refactoring to use more DI. This works in geronimo assembled using blueprint, but I don't have a good way to test the spring assembly, which may well not work properly. Please let me know of problems and I will work to fix them.
        Hide
        David Jencks added a comment -

        As of rev 889103 I have pluto running in geronimo under osgi wired using blueprint. There are some bits of code still at geronimo. This commit:

        1. fixes poms to generate working osgi metadata
        2. Adds some DI constructors to avoid requiring components to read their own configuration files
        3. For the read-your-own-config-file approack, abstracts away from direct use of ServletContext to find the files.
        4. provides hardcoded defaults for ToolTIps resourse bundles in case osgi can't find the appropriate properties file(s).

        With the possible exception of (3) I would not expect these to impact embedders of pluto.

        Show
        David Jencks added a comment - As of rev 889103 I have pluto running in geronimo under osgi wired using blueprint. There are some bits of code still at geronimo. This commit: 1. fixes poms to generate working osgi metadata 2. Adds some DI constructors to avoid requiring components to read their own configuration files 3. For the read-your-own-config-file approack, abstracts away from direct use of ServletContext to find the files. 4. provides hardcoded defaults for ToolTIps resourse bundles in case osgi can't find the appropriate properties file(s). With the possible exception of (3) I would not expect these to impact embedders of pluto.
        Hide
        David Jencks added a comment -

        rev 886700 builds bundles instead of plain jars and makes a few osgi package imports optional. I can get all the jars to load in geronimo but don't know if anything works yet.

        Show
        David Jencks added a comment - rev 886700 builds bundles instead of plain jars and makes a few osgi package imports optional. I can get all the jars to load in geronimo but don't know if anything works yet.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development