Jackson: Property can be raw, arbitrary object or POJO












0














Let's say I use Jackson to serialize and deserialize POJOs. I have a number of classes like this:



class Foo {
String field1;
Bar field2;
// ...
Baz baz;
}


Where baz is a large JSON object that I receive from an external system. I want to use Foo in three different ways:




  1. Serialize Foo and include baz without even bothering to parse it, as if I had declared it as @JsonRawValue String baz.

  2. Pretty-print Foo and include baz just like I received it except pretty-printed, as if I had declared it as Map<String, Object> baz.

  3. Pass Foo to my business logic, with baz deserialized to a POJO, as in the code above.


One way to do this would be to declare three classes, with the baz field declared in three different ways. I could also combine 2) and 3) into a single class with @JsonAnySetter and @JsonAnyGetter to capture any properties I don't recognize.



But is there a clean way to support all the three use cases above while declaring just a single Foo class?










share|improve this question



























    0














    Let's say I use Jackson to serialize and deserialize POJOs. I have a number of classes like this:



    class Foo {
    String field1;
    Bar field2;
    // ...
    Baz baz;
    }


    Where baz is a large JSON object that I receive from an external system. I want to use Foo in three different ways:




    1. Serialize Foo and include baz without even bothering to parse it, as if I had declared it as @JsonRawValue String baz.

    2. Pretty-print Foo and include baz just like I received it except pretty-printed, as if I had declared it as Map<String, Object> baz.

    3. Pass Foo to my business logic, with baz deserialized to a POJO, as in the code above.


    One way to do this would be to declare three classes, with the baz field declared in three different ways. I could also combine 2) and 3) into a single class with @JsonAnySetter and @JsonAnyGetter to capture any properties I don't recognize.



    But is there a clean way to support all the three use cases above while declaring just a single Foo class?










    share|improve this question

























      0












      0








      0







      Let's say I use Jackson to serialize and deserialize POJOs. I have a number of classes like this:



      class Foo {
      String field1;
      Bar field2;
      // ...
      Baz baz;
      }


      Where baz is a large JSON object that I receive from an external system. I want to use Foo in three different ways:




      1. Serialize Foo and include baz without even bothering to parse it, as if I had declared it as @JsonRawValue String baz.

      2. Pretty-print Foo and include baz just like I received it except pretty-printed, as if I had declared it as Map<String, Object> baz.

      3. Pass Foo to my business logic, with baz deserialized to a POJO, as in the code above.


      One way to do this would be to declare three classes, with the baz field declared in three different ways. I could also combine 2) and 3) into a single class with @JsonAnySetter and @JsonAnyGetter to capture any properties I don't recognize.



      But is there a clean way to support all the three use cases above while declaring just a single Foo class?










      share|improve this question













      Let's say I use Jackson to serialize and deserialize POJOs. I have a number of classes like this:



      class Foo {
      String field1;
      Bar field2;
      // ...
      Baz baz;
      }


      Where baz is a large JSON object that I receive from an external system. I want to use Foo in three different ways:




      1. Serialize Foo and include baz without even bothering to parse it, as if I had declared it as @JsonRawValue String baz.

      2. Pretty-print Foo and include baz just like I received it except pretty-printed, as if I had declared it as Map<String, Object> baz.

      3. Pass Foo to my business logic, with baz deserialized to a POJO, as in the code above.


      One way to do this would be to declare three classes, with the baz field declared in three different ways. I could also combine 2) and 3) into a single class with @JsonAnySetter and @JsonAnyGetter to capture any properties I don't recognize.



      But is there a clean way to support all the three use cases above while declaring just a single Foo class?







      jackson






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 23 '18 at 8:35









      Aapo Laitinen

      371210




      371210
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53443129%2fjackson-property-can-be-raw-arbitrary-object-or-pojo%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53443129%2fjackson-property-can-be-raw-arbitrary-object-or-pojo%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          What visual should I use to simply compare current year value vs last year in Power BI desktop

          How to ignore python UserWarning in pytest?

          Alexandru Averescu