Explicitly parse JSON string vs JSON.deserialize The 2019 Stack Overflow Developer Survey Results Are InJSON and escaped double quoteParse nested JSONJSON parsing to Visualforce page difficultiesDefault values for Wrapper variables not setConvert date in JSON to Date from StringMethod does not exist or incorrect signature: void parse(String) from the type or_propertyJSONTestHow to parse JSON String through apexDeserializing/Parsing the JSON response to an Apex classJson2apex - Message consuming unrecognized propertyParse JSON using APEX provided JSON Methods

What are the motivations for publishing new editions of an existing textbook, beyond new discoveries in a field?

Button changing it's text & action. Good or terrible?

Earliest use of the term "Galois extension"?

How can I autofill dates in Excel excluding Sunday?

Loose spokes after only a few rides

What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?

Aging parents with no investments

Why was M87 targetted for the Event Horizon Telescope instead of Sagittarius A*?

Why didn't the Event Horizon Telescope team mention Sagittarius A*?

Can someone be penalized for an "unlawful" act if no penalty is specified?

A poker game description that does not feel gimmicky

When should I buy a clipper card after flying to OAK?

Should I use my personal e-mail address, or my workplace one, when registering to external websites for work purposes?

FPGA - DIY Programming

Origin of "cooter" meaning "vagina"

Worn-tile Scrabble

Falsification in Math vs Science

What do the Banks children have against barley water?

Is this app Icon Browser Safe/Legit?

Pokemon Turn Based battle (Python)

What is the meaning of Triage in Cybersec world?

How to notate time signature switching consistently every measure

Lightning Grid - Columns and Rows?

Is a "Democratic" Oligarchy-Style System Possible?



Explicitly parse JSON string vs JSON.deserialize



The 2019 Stack Overflow Developer Survey Results Are InJSON and escaped double quoteParse nested JSONJSON parsing to Visualforce page difficultiesDefault values for Wrapper variables not setConvert date in JSON to Date from StringMethod does not exist or incorrect signature: void parse(String) from the type or_propertyJSONTestHow to parse JSON String through apexDeserializing/Parsing the JSON response to an Apex classJson2apex - Message consuming unrecognized propertyParse JSON using APEX provided JSON Methods



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1















The JSON2Apex web tool offers 2 methods of parsing of the JSON string: one uses JSON.deserialize method, and the other creates parser and iterates over the input json. The second option can be enabled by checking "Create explicit parse code" in the tool.



QUESTION



In what cases would a developer prefer explicit parsing to a simple JSON.deserialize? If we compare both options the later seems to be much clear and less verbose which makes code more readable.



Explicit parsing



public class JSON2Apex 

public class User
public String name get;set;
public String twitter get;set;

public User(JSONParser parser)
while (parser.nextToken() != System.JSONToken.END_OBJECT)
if (parser.getCurrentToken() == System.JSONToken.FIELD_NAME)
String text = parser.getText();
if (parser.nextToken() != System.JSONToken.VALUE_NULL)
if (text == 'name')
name = parser.getText();
else if (text == 'twitter')
twitter = parser.getText();
else
System.debug(LoggingLevel.WARN, 'User consuming unrecognized property: '+text);
consumeObject(parser);







public User user get;set;

public JSON2Apex(JSONParser parser)
while (parser.nextToken() != System.JSONToken.END_OBJECT)
if (parser.getCurrentToken() == System.JSONToken.FIELD_NAME)
String text = parser.getText();
if (parser.nextToken() != System.JSONToken.VALUE_NULL)
if (text == 'user')
user = new User(parser);
else
System.debug(LoggingLevel.WARN, 'JSON2Apex consuming unrecognized property: '+text);
consumeObject(parser);







public static JSON2Apex parse(String json)
System.JSONParser parser = System.JSON.createParser(json);
return new JSON2Apex(parser);


public static void consumeObject(System.JSONParser parser)
Integer depth = 0;
do
System.JSONToken curr = parser.getCurrentToken();
if (curr == System.JSONToken.START_OBJECT while (depth > 0 && parser.nextToken() != null);








JSON.deserialize



public class JSON2Apex 

public class User
public String name;
public String twitter;


public User user;


public static JSON2Apex parse(String json)
return (JSON2Apex) System.JSON.deserialize(json, JSON2Apex.class);











share|improve this question




























    1















    The JSON2Apex web tool offers 2 methods of parsing of the JSON string: one uses JSON.deserialize method, and the other creates parser and iterates over the input json. The second option can be enabled by checking "Create explicit parse code" in the tool.



    QUESTION



    In what cases would a developer prefer explicit parsing to a simple JSON.deserialize? If we compare both options the later seems to be much clear and less verbose which makes code more readable.



    Explicit parsing



    public class JSON2Apex 

    public class User
    public String name get;set;
    public String twitter get;set;

    public User(JSONParser parser)
    while (parser.nextToken() != System.JSONToken.END_OBJECT)
    if (parser.getCurrentToken() == System.JSONToken.FIELD_NAME)
    String text = parser.getText();
    if (parser.nextToken() != System.JSONToken.VALUE_NULL)
    if (text == 'name')
    name = parser.getText();
    else if (text == 'twitter')
    twitter = parser.getText();
    else
    System.debug(LoggingLevel.WARN, 'User consuming unrecognized property: '+text);
    consumeObject(parser);







    public User user get;set;

    public JSON2Apex(JSONParser parser)
    while (parser.nextToken() != System.JSONToken.END_OBJECT)
    if (parser.getCurrentToken() == System.JSONToken.FIELD_NAME)
    String text = parser.getText();
    if (parser.nextToken() != System.JSONToken.VALUE_NULL)
    if (text == 'user')
    user = new User(parser);
    else
    System.debug(LoggingLevel.WARN, 'JSON2Apex consuming unrecognized property: '+text);
    consumeObject(parser);







    public static JSON2Apex parse(String json)
    System.JSONParser parser = System.JSON.createParser(json);
    return new JSON2Apex(parser);


    public static void consumeObject(System.JSONParser parser)
    Integer depth = 0;
    do
    System.JSONToken curr = parser.getCurrentToken();
    if (curr == System.JSONToken.START_OBJECT while (depth > 0 && parser.nextToken() != null);








    JSON.deserialize



    public class JSON2Apex 

    public class User
    public String name;
    public String twitter;


    public User user;


    public static JSON2Apex parse(String json)
    return (JSON2Apex) System.JSON.deserialize(json, JSON2Apex.class);











    share|improve this question
























      1












      1








      1








      The JSON2Apex web tool offers 2 methods of parsing of the JSON string: one uses JSON.deserialize method, and the other creates parser and iterates over the input json. The second option can be enabled by checking "Create explicit parse code" in the tool.



      QUESTION



      In what cases would a developer prefer explicit parsing to a simple JSON.deserialize? If we compare both options the later seems to be much clear and less verbose which makes code more readable.



      Explicit parsing



      public class JSON2Apex 

      public class User
      public String name get;set;
      public String twitter get;set;

      public User(JSONParser parser)
      while (parser.nextToken() != System.JSONToken.END_OBJECT)
      if (parser.getCurrentToken() == System.JSONToken.FIELD_NAME)
      String text = parser.getText();
      if (parser.nextToken() != System.JSONToken.VALUE_NULL)
      if (text == 'name')
      name = parser.getText();
      else if (text == 'twitter')
      twitter = parser.getText();
      else
      System.debug(LoggingLevel.WARN, 'User consuming unrecognized property: '+text);
      consumeObject(parser);







      public User user get;set;

      public JSON2Apex(JSONParser parser)
      while (parser.nextToken() != System.JSONToken.END_OBJECT)
      if (parser.getCurrentToken() == System.JSONToken.FIELD_NAME)
      String text = parser.getText();
      if (parser.nextToken() != System.JSONToken.VALUE_NULL)
      if (text == 'user')
      user = new User(parser);
      else
      System.debug(LoggingLevel.WARN, 'JSON2Apex consuming unrecognized property: '+text);
      consumeObject(parser);







      public static JSON2Apex parse(String json)
      System.JSONParser parser = System.JSON.createParser(json);
      return new JSON2Apex(parser);


      public static void consumeObject(System.JSONParser parser)
      Integer depth = 0;
      do
      System.JSONToken curr = parser.getCurrentToken();
      if (curr == System.JSONToken.START_OBJECT while (depth > 0 && parser.nextToken() != null);








      JSON.deserialize



      public class JSON2Apex 

      public class User
      public String name;
      public String twitter;


      public User user;


      public static JSON2Apex parse(String json)
      return (JSON2Apex) System.JSON.deserialize(json, JSON2Apex.class);











      share|improve this question














      The JSON2Apex web tool offers 2 methods of parsing of the JSON string: one uses JSON.deserialize method, and the other creates parser and iterates over the input json. The second option can be enabled by checking "Create explicit parse code" in the tool.



      QUESTION



      In what cases would a developer prefer explicit parsing to a simple JSON.deserialize? If we compare both options the later seems to be much clear and less verbose which makes code more readable.



      Explicit parsing



      public class JSON2Apex 

      public class User
      public String name get;set;
      public String twitter get;set;

      public User(JSONParser parser)
      while (parser.nextToken() != System.JSONToken.END_OBJECT)
      if (parser.getCurrentToken() == System.JSONToken.FIELD_NAME)
      String text = parser.getText();
      if (parser.nextToken() != System.JSONToken.VALUE_NULL)
      if (text == 'name')
      name = parser.getText();
      else if (text == 'twitter')
      twitter = parser.getText();
      else
      System.debug(LoggingLevel.WARN, 'User consuming unrecognized property: '+text);
      consumeObject(parser);







      public User user get;set;

      public JSON2Apex(JSONParser parser)
      while (parser.nextToken() != System.JSONToken.END_OBJECT)
      if (parser.getCurrentToken() == System.JSONToken.FIELD_NAME)
      String text = parser.getText();
      if (parser.nextToken() != System.JSONToken.VALUE_NULL)
      if (text == 'user')
      user = new User(parser);
      else
      System.debug(LoggingLevel.WARN, 'JSON2Apex consuming unrecognized property: '+text);
      consumeObject(parser);







      public static JSON2Apex parse(String json)
      System.JSONParser parser = System.JSON.createParser(json);
      return new JSON2Apex(parser);


      public static void consumeObject(System.JSONParser parser)
      Integer depth = 0;
      do
      System.JSONToken curr = parser.getCurrentToken();
      if (curr == System.JSONToken.START_OBJECT while (depth > 0 && parser.nextToken() != null);








      JSON.deserialize



      public class JSON2Apex 

      public class User
      public String name;
      public String twitter;


      public User user;


      public static JSON2Apex parse(String json)
      return (JSON2Apex) System.JSON.deserialize(json, JSON2Apex.class);








      json parsing






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked yesterday









      EduardEduard

      1,8872723




      1,8872723




















          1 Answer
          1






          active

          oldest

          votes


















          4














          Apex code has reserved names (keywords) and special variable rules (e.g. cannot start with a number, can't have __, etc) that you can't use in JSON objects. You don't want to use explicit mode if you can help it, because it has worse performance compared to JSON.deserialize, but it gets around compilation errors if you have a JSON string like:



           "title": "Writing JSON", "abstract": "A short document about how to use JSON." 


          This would compile to:



          public class JSON2Apex 
          public String title;
          public String abstract;



          But abstract is a reserved keyword. You can't deploy this code to Salesforce. By changing the code:



          public class JSON2Apex 
          public String title;
          public String abstract_x;



          The code can then compile, but you need explicit parsing in order to translate abstract in the JSON string to abstract_x in Apex.






          share|improve this answer























          • Thanks for your prompt answer! If this is the only reason why a developer would use explicit parsing, then I would definitely go with deserialize all the time. It's possible to keep a Map of reserved words and their substitutes, and perform replace in the input json string before parsing. This is exaclty how the ffhttp_JsonDeserializer.cls class works.

            – Eduard
            yesterday






          • 1





            @Eduard Yes, there are better ways. JSON2Apex is a rather old utility, useful in most cases, but explicit mode wasn't the best idea. There's definitely better ways to do it.

            – sfdcfox
            yesterday











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "459"
          ;
          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: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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%2fsalesforce.stackexchange.com%2fquestions%2f257118%2fexplicitly-parse-json-string-vs-json-deserialize%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          4














          Apex code has reserved names (keywords) and special variable rules (e.g. cannot start with a number, can't have __, etc) that you can't use in JSON objects. You don't want to use explicit mode if you can help it, because it has worse performance compared to JSON.deserialize, but it gets around compilation errors if you have a JSON string like:



           "title": "Writing JSON", "abstract": "A short document about how to use JSON." 


          This would compile to:



          public class JSON2Apex 
          public String title;
          public String abstract;



          But abstract is a reserved keyword. You can't deploy this code to Salesforce. By changing the code:



          public class JSON2Apex 
          public String title;
          public String abstract_x;



          The code can then compile, but you need explicit parsing in order to translate abstract in the JSON string to abstract_x in Apex.






          share|improve this answer























          • Thanks for your prompt answer! If this is the only reason why a developer would use explicit parsing, then I would definitely go with deserialize all the time. It's possible to keep a Map of reserved words and their substitutes, and perform replace in the input json string before parsing. This is exaclty how the ffhttp_JsonDeserializer.cls class works.

            – Eduard
            yesterday






          • 1





            @Eduard Yes, there are better ways. JSON2Apex is a rather old utility, useful in most cases, but explicit mode wasn't the best idea. There's definitely better ways to do it.

            – sfdcfox
            yesterday















          4














          Apex code has reserved names (keywords) and special variable rules (e.g. cannot start with a number, can't have __, etc) that you can't use in JSON objects. You don't want to use explicit mode if you can help it, because it has worse performance compared to JSON.deserialize, but it gets around compilation errors if you have a JSON string like:



           "title": "Writing JSON", "abstract": "A short document about how to use JSON." 


          This would compile to:



          public class JSON2Apex 
          public String title;
          public String abstract;



          But abstract is a reserved keyword. You can't deploy this code to Salesforce. By changing the code:



          public class JSON2Apex 
          public String title;
          public String abstract_x;



          The code can then compile, but you need explicit parsing in order to translate abstract in the JSON string to abstract_x in Apex.






          share|improve this answer























          • Thanks for your prompt answer! If this is the only reason why a developer would use explicit parsing, then I would definitely go with deserialize all the time. It's possible to keep a Map of reserved words and their substitutes, and perform replace in the input json string before parsing. This is exaclty how the ffhttp_JsonDeserializer.cls class works.

            – Eduard
            yesterday






          • 1





            @Eduard Yes, there are better ways. JSON2Apex is a rather old utility, useful in most cases, but explicit mode wasn't the best idea. There's definitely better ways to do it.

            – sfdcfox
            yesterday













          4












          4








          4







          Apex code has reserved names (keywords) and special variable rules (e.g. cannot start with a number, can't have __, etc) that you can't use in JSON objects. You don't want to use explicit mode if you can help it, because it has worse performance compared to JSON.deserialize, but it gets around compilation errors if you have a JSON string like:



           "title": "Writing JSON", "abstract": "A short document about how to use JSON." 


          This would compile to:



          public class JSON2Apex 
          public String title;
          public String abstract;



          But abstract is a reserved keyword. You can't deploy this code to Salesforce. By changing the code:



          public class JSON2Apex 
          public String title;
          public String abstract_x;



          The code can then compile, but you need explicit parsing in order to translate abstract in the JSON string to abstract_x in Apex.






          share|improve this answer













          Apex code has reserved names (keywords) and special variable rules (e.g. cannot start with a number, can't have __, etc) that you can't use in JSON objects. You don't want to use explicit mode if you can help it, because it has worse performance compared to JSON.deserialize, but it gets around compilation errors if you have a JSON string like:



           "title": "Writing JSON", "abstract": "A short document about how to use JSON." 


          This would compile to:



          public class JSON2Apex 
          public String title;
          public String abstract;



          But abstract is a reserved keyword. You can't deploy this code to Salesforce. By changing the code:



          public class JSON2Apex 
          public String title;
          public String abstract_x;



          The code can then compile, but you need explicit parsing in order to translate abstract in the JSON string to abstract_x in Apex.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered yesterday









          sfdcfoxsfdcfox

          264k13210457




          264k13210457












          • Thanks for your prompt answer! If this is the only reason why a developer would use explicit parsing, then I would definitely go with deserialize all the time. It's possible to keep a Map of reserved words and their substitutes, and perform replace in the input json string before parsing. This is exaclty how the ffhttp_JsonDeserializer.cls class works.

            – Eduard
            yesterday






          • 1





            @Eduard Yes, there are better ways. JSON2Apex is a rather old utility, useful in most cases, but explicit mode wasn't the best idea. There's definitely better ways to do it.

            – sfdcfox
            yesterday

















          • Thanks for your prompt answer! If this is the only reason why a developer would use explicit parsing, then I would definitely go with deserialize all the time. It's possible to keep a Map of reserved words and their substitutes, and perform replace in the input json string before parsing. This is exaclty how the ffhttp_JsonDeserializer.cls class works.

            – Eduard
            yesterday






          • 1





            @Eduard Yes, there are better ways. JSON2Apex is a rather old utility, useful in most cases, but explicit mode wasn't the best idea. There's definitely better ways to do it.

            – sfdcfox
            yesterday
















          Thanks for your prompt answer! If this is the only reason why a developer would use explicit parsing, then I would definitely go with deserialize all the time. It's possible to keep a Map of reserved words and their substitutes, and perform replace in the input json string before parsing. This is exaclty how the ffhttp_JsonDeserializer.cls class works.

          – Eduard
          yesterday





          Thanks for your prompt answer! If this is the only reason why a developer would use explicit parsing, then I would definitely go with deserialize all the time. It's possible to keep a Map of reserved words and their substitutes, and perform replace in the input json string before parsing. This is exaclty how the ffhttp_JsonDeserializer.cls class works.

          – Eduard
          yesterday




          1




          1





          @Eduard Yes, there are better ways. JSON2Apex is a rather old utility, useful in most cases, but explicit mode wasn't the best idea. There's definitely better ways to do it.

          – sfdcfox
          yesterday





          @Eduard Yes, there are better ways. JSON2Apex is a rather old utility, useful in most cases, but explicit mode wasn't the best idea. There's definitely better ways to do it.

          – sfdcfox
          yesterday

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Salesforce Stack Exchange!


          • 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%2fsalesforce.stackexchange.com%2fquestions%2f257118%2fexplicitly-parse-json-string-vs-json-deserialize%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

          Category:9 (number) SubcategoriesMedia in category "9 (number)"Navigation menuUpload mediaGND ID: 4485639-8Library of Congress authority ID: sh85091979ReasonatorScholiaStatistics

          Circuit construction for execution of conditional statements using least significant bitHow are two different registers being used as “control”?How exactly is the stated composite state of the two registers being produced using the $R_zz$ controlled rotations?Efficiently performing controlled rotations in HHLWould this quantum algorithm implementation work?How to prepare a superposed states of odd integers from $1$ to $sqrtN$?Why is this implementation of the order finding algorithm not working?Circuit construction for Hamiltonian simulationHow can I invert the least significant bit of a certain term of a superposed state?Implementing an oracleImplementing a controlled sum operation

          Magento 2 “No Payment Methods” in Admin New OrderHow to integrate Paypal Express Checkout with the Magento APIMagento 1.5 - Sales > Order > edit order and shipping methods disappearAuto Invoice Check/Money Order Payment methodAdd more simple payment methods?Shipping methods not showingWhat should I do to change payment methods if changing the configuration has no effects?1.9 - No Payment Methods showing upMy Payment Methods not Showing for downloadable/virtual product when checkout?Magento2 API to access internal payment methodHow to call an existing payment methods in the registration form?