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

Improve cockpit error message for parsing errors during deplyoment

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • cockpit
    • None

      Scenario:
      when deploying a bpmn file in cockpit which triggers a parser exception I get the following error message in Cockpit :

      Communication Error : The application received an unexpected 400 response from the server. Try to refresh the page or login and out of the application.

      error message in the server log:

      org.camunda.bpm.engine.ParseException: ENGINE-09005 Could not parse BPMN process. Errors: 
* One of the attributes 'class', 'delegateExpression', 'type', or 'expression' is mandatory on businessRuleTask. | resource call_dmn.bpmn | line 17 | column 66

      Problem:
      The user gets no information about the root cause of the error and a suggestion which does not solve the problem

      AT:
      Display a more meaningful error message in cockpit

        This is the controller panel for Smart Panels app

            [CAM-11768] Improve cockpit error message for parsing errors during deplyoment

            Michael Schoettes created issue -

            Thorben Lindhauer added a comment -

            We are closing this ticket as part of our backlog grooming. Reasons:

            • We did not receive sufficient evidence that this ticket is important

            Thorben Lindhauer added a comment - We are closing this ticket as part of our backlog grooming. Reasons: We did not receive sufficient evidence that this ticket is important
            Thorben Lindhauer made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]

              Unassigned Unassigned
              michael.schoettes Michael Schoettes
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: