Uploaded image for project: 'Felix'
  1. Felix
  2. FELIX-5448

Exceptions from bundle.start() should be logged, not swallowed

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: fileinstall-3.5.4
    • Fix Version/s: fileinstall-3.6.2
    • Component/s: File Install
    • Labels:
      None

      Description

      based on http://stackoverflow.com/questions/41092687/how-to-see-why-bundle-requirements-are-not-fulfilled-in-apache-felix-log/ :

      Isn't it a bug that File Install silently "swallows" (ignore, drops; does not log) any issues thrown when it (re)loads bundle and bundle.start() them?

      Or are there valid use cases and reasons I'm missing why this "sinking" of bundle load errors may be intentional?

      It's definitely a PITA to discover e.g. load issues by having to manually go into a Console, and lb and start - instead of just seeing them in the log.

      Would a code contribution proposing a fix for this be welcome?

        Attachments

          Activity

            People

            • Assignee:
              gnodet Guillaume Nodet
              Reporter:
              vorburger Michael Vorburger
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: