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

Use objectMapper bean for spin/jackson configuration

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • spring-boot 3.2.1
    • spin, spring-boot
    • None

      The objectMapper used for spin json serializaition with spin is currently configured via Service Locator (META-INF/services).

      If we already have an objectMapper bean configured in the spring context, there should be an easy (default) way of reusing this bean for camunda/spin.

        This is the controller panel for Smart Panels app

            [CAM-10199] Use objectMapper bean for spin/jackson configuration

            Tobias Metzke-Bernstein added a comment - - edited

            Hi Jan,

            thanks for opening this.

            In order to get a better understanding and a more detailed discussion basis for this, would you mind providing a basic working setup on how this has to be done at the moment and how you would expect it to work in the future?
            A PR with a first solution outline could be a good starting point for this as well.

            Besides, is this in the scope of a project with an existing Camunda customer?

            Thanks for working with us on this.

            Best,
            Tobias

            Tobias Metzke-Bernstein added a comment - - edited Hi Jan, thanks for opening this. In order to get a better understanding and a more detailed discussion basis for this, would you mind providing a basic working setup on how this has to be done at the moment and how you would expect it to work in the future? A PR with a first solution outline could be a good starting point for this as well. Besides, is this in the scope of a project with an existing Camunda customer? Thanks for working with us on this. Best, Tobias

            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

              Unassigned Unassigned
              jan.galinski@holisticon.de Jan Galinski
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: