Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-8407

Wrong exception processing in SpringArtifactFactory

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.8.0, 7.8.0-alpha6
    • None
    • engine
    • None

      Steps to reproduce

      • we reference the bean in camunda:class, which does not exist in application context

      Actual result:

      • BeansException is thrown and it is not processed in code (instead null-check is there)

      Expected result:

      • The exception is being caught and the class is instantiated by DefaultArtifactFactory

      + test case is missing

      Also see comment here:
      https://github.com/camunda/camunda-bpm-platform/commit/f78e6d2055d8e0674baa38834f99efc89fc5155b#diff-7bb5d75091c47a0692d9f1da79615ec0R37

        This is the controller panel for Smart Panels app

            [CAM-8407] Wrong exception processing in SpringArtifactFactory

            Svetlana Dorokhova created issue -
            Svetlana Dorokhova made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Svetlana Dorokhova made changes -
            Summary Original: Wrong exception processing in New: Wrong exception processing in SpringArtifactFactory
            Svetlana Dorokhova made changes -
            Description Original: When
             * we reference the bean in {{camunda:class}}, which does not exist in application context

            Then
             * BeansException is thrown and it is not processed in code (instead null-check is there)

            + test case is missing

            Also see comment here:
            https://github.com/camunda/camunda-bpm-platform/commit/f78e6d2055d8e0674baa38834f99efc89fc5155b#diff-7bb5d75091c47a0692d9f1da79615ec0R37             		New: Steps to reproduce
             * we reference the bean in {{camunda:class}}, which does not exist in application context

            Actual result:
             * BeansException is thrown and it is not processed in code (instead null-check is there)

            Expected result:
             * The exception is being caught and the class is instantiated by DefaultArtifactFactory

            + test case is missing

            Also see comment here:
            https://github.com/camunda/camunda-bpm-platform/commit/f78e6d2055d8e0674baa38834f99efc89fc5155b#diff-7bb5d75091c47a0692d9f1da79615ec0R37
            Svetlana Dorokhova made changes -
            Assignee Original: Svetlana Dorokhova [ svetlana.dorokhova ] New: Yana Vasileva [ yana.vasileva ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            Remaining Estimate New: 0 minutes [ 0 ]
            Original Estimate New: 0 minutes [ 0 ]
            Yana Vasileva made changes -
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Yana Vasileva made changes -
            Fix Version/s New: 7.8.0-alpha6 [ 15101 ]
            Thorben Lindhauer made changes -
            Workflow Original: camunda BPM [ 44447 ] New: Backup_camunda BPM [ 63321 ]

              yana.vasileva Yana Vasileva
              svetlana.dorokhova Svetlana Dorokhova
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: