We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
We couldn't load the project sidebar. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12429

Centralize property validation in the bridge

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • rpa
    • None

      The bridge's properties should be validated in a central manner, ideally very early in application startup. This will improve the error messages users receive on misconfiguration as they will see all mistakes at once and not only the first ones that fail, followed by new failures after fixing the first ones.

      Hint
      We could do this centrally in the BridgeProperties class or in the single property classes, using the instructions from here: https://reflectoring.io/validate-spring-boot-configuration-parameters-at-startup/
      However, when doing this in the nested property classes, implementing the Validator interface will not trigger those classes to be validated somehow (only worked in the BridgeProperties class for me on first try, probably because only this class is annotated with @ConfigurationProperties)

        This is the controller panel for Smart Panels app

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

            Centralize property validation in the bridge

              • Icon: Task Task
              • Resolution: Unresolved
              • Icon: L3 - Default L3 - Default
              • None
              • None
              • rpa
              • None

                The bridge's properties should be validated in a central manner, ideally very early in application startup. This will improve the error messages users receive on misconfiguration as they will see all mistakes at once and not only the first ones that fail, followed by new failures after fixing the first ones.

                Hint
                We could do this centrally in the BridgeProperties class or in the single property classes, using the instructions from here: https://reflectoring.io/validate-spring-boot-configuration-parameters-at-startup/
                However, when doing this in the nested property classes, implementing the Validator interface will not trigger those classes to be validated somehow (only worked in the BridgeProperties class for me on first try, probably because only this class is annotated with @ConfigurationProperties)

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        tobias.metzke Tobias Metzke-Bernstein
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:

                              Unassigned Unassigned
                              tobias.metzke Tobias Metzke-Bernstein
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              2 Start watching this issue

                                Created:
                                Updated: