Uploaded image for project: 'OODT'
  1. OODT
  2. OODT-910

Create Skinny Dependencies for WARs

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • opsui
    • None
    • Don't Know (Unsure) - The default level

    Description

      Currently the OPSUI war files are huge because the drag in all of the OODT component transient dependencies which to the best of my knowledge are generally not required as the UI just sends commands to remote services.

      To combat this we should create some skinny components that dont' include all the transient dependencies.

      The "easy" but not very maintainable way would probably be to "exclude" a big list of transient dependencies in the pom files for the components you want to slim down.

      An alternative approach which I would favour, would be to create an API module, similar to OSGI design practices, that contain the various API interfaces for the component, say the filemanager. Then OPSUI can implement its required interfaces separately from the filemanager, which can also implement the interfaces if required on its side.

      I'm sure there are alternatives, just dictating my thoughts.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bugg_tb Tom Barber
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: