Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-1630

Engine Fetcher uses optimize dateTimeFormatter instead of the engine dateFormatter

    Details

    • Type: Bug Report
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4.0, 2.4.0-alpha2
    • Component/s: backend
    • Labels:
      None

      Description

      currently engine fetchers get the dateformatter injected with:

        @Autowired
        private DateTimeFormatter dateTimeFormatter;
      

      which means they get the optimizeDateFormatter as this is the only one provided by a beanFactory. We need to use qualifiers for correct injection like for objectMappers.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            sebastian.bathke Sebastian Bathke
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: