Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-1922

Refresh OSGI modules after new build.

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Sprint:
      Summer 2019 Sprint 11, Summer 2019 Sprint 12, Fall 2019 Sprint 1

      Description

      1. Refreshing/ Updating OSGi modules using the Apache web console is breaking the UI.
      2. Try refreshing OSGI modules automatically after new build.

        Attachments

          Issue Links

            Activity

            Hide
            svallapu Sai Charan Reddy Vallapureddy added a comment -

            I tried all the ways to refresh/update bundles using Apache web console. But if we refresh bundles using web console IGB UI is breaking.

            Show
            svallapu Sai Charan Reddy Vallapureddy added a comment - I tried all the ways to refresh/update bundles using Apache web console. But if we refresh bundles using web console IGB UI is breaking.
            Hide
            svallapu Sai Charan Reddy Vallapureddy added a comment - - edited

            Useful links:
            http://www.solutionsfit.com/2008/08/27/osgi-what-modularity-can-do-for-you-part-1/

            Discusson our problem: https://stackoverflow.com/questions/4330927/how-does-osgi-bundle-update-work

            The conclusion from the above discussion thread.
            1. We cant use update command for updating a single module.
            2. Update command should be used when we are introducing a new version of the same bundle, to be only supplied to dependent bundles that are yet to come, -which are not yet there at the time of the update.
            3. Solution: 'refresh' command without specifying a specific bundle, meaning that all bundles will be blindly refreshed. The 'refresh' command forces the rebuilding of the dependency tree of the target bundles, and coerce their class loaders to start loading their required classes from scratch.

            Show
            svallapu Sai Charan Reddy Vallapureddy added a comment - - edited Useful links: http://www.solutionsfit.com/2008/08/27/osgi-what-modularity-can-do-for-you-part-1/ Discusson our problem: https://stackoverflow.com/questions/4330927/how-does-osgi-bundle-update-work The conclusion from the above discussion thread. 1. We cant use update command for updating a single module. 2. Update command should be used when we are introducing a new version of the same bundle, to be only supplied to dependent bundles that are yet to come, -which are not yet there at the time of the update. 3. Solution: 'refresh' command without specifying a specific bundle, meaning that all bundles will be blindly refreshed. The 'refresh' command forces the rebuilding of the dependency tree of the target bundles, and coerce their class loaders to start loading their required classes from scratch.
            Hide
            svallapu Sai Charan Reddy Vallapureddy added a comment -

            https://felix.apache.org/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html

            Official statement: When you use felix:update or felix:uninstall, the changes appear to take effect immediately, but in reality the changes are only partially enacted. If a bundle is updated or uninstalled and it was exporting packages, these packages are not removed until the framework is refreshed using the PackageAdmin service. The Felix shell offers a convenient refresh command for this purpose. This is the correct behavior as defined by the OSGi specification.

            Show
            svallapu Sai Charan Reddy Vallapureddy added a comment - https://felix.apache.org/documentation/subprojects/apache-felix-framework/apache-felix-framework-usage-documentation.html Official statement: When you use felix:update or felix:uninstall, the changes appear to take effect immediately, but in reality the changes are only partially enacted. If a bundle is updated or uninstalled and it was exporting packages, these packages are not removed until the framework is refreshed using the PackageAdmin service. The Felix shell offers a convenient refresh command for this purpose. This is the correct behavior as defined by the OSGi specification.
            Hide
            aloraine Ann Loraine added a comment -

            Looks like we have reached the limit of what felix web console can do for us.
            Am marking this as Closed.
            We still need to incorporate this new information into instructions for developers - that can be a separate, linked ticket.

            Show
            aloraine Ann Loraine added a comment - Looks like we have reached the limit of what felix web console can do for us. Am marking this as Closed. We still need to incorporate this new information into instructions for developers - that can be a separate, linked ticket.

              People

              • Assignee:
                svallapu Sai Charan Reddy Vallapureddy
                Reporter:
                svallapu Sai Charan Reddy Vallapureddy
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: