Fix objectMapper inconsistency

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 2.3.0-alpha2, 2.3.0
    • Affects Version/s: None
    • Component/s: backend
    • None

      Currently OptimizeObjectMapperProvider is used for both the optimize Rest api + the engine client. Further the provider currently creates a new mapper everytime it's called, it could just cache the mapper once.

      AT:

      • the engine client uses a dedicated engine mapper
      • the rest api uses the optimizeMapper
      • mappers are not recreated for each call to *ContextResolvers

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: