Details

    • Type: Bug Bug
    • Status: Resolved Resolved (View Workflow)
    • Priority: Minor Minor
    • Resolution: Rejected
    • Affects Version/s: 3.2.1.001
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Mac OS X, Railo 3.2/Tomcat Apache
    • Similar Issues:
      Show 10 results 

      Description

      In Railo 3.2, using DeserializeJSON give different result from Railo 3.1 when there is a NULL value

      Example Code:

      <cfsavecontent variable="jsonStr">
      [

      { "hero": "Spiderman", "heroine": "Mary Jane" }

      ,

      { "hero": "Superman", "heroine": "Lois Lane" }

      ,

      { "hero": "Batman", "heroine": null }

      ,

      { "hero": "Captain America", "heroine": "" }

      ]

      </cfsavecontent>
      <cfdump var="#DeserializeJSON(jsonStr)#">

        Activity

        Hide
        Peter Pham
        added a comment -

        result from Railo 3.2, Coldfusion 9 and Railo 3.1

        Show
        Peter Pham
        added a comment - result from Railo 3.2, Coldfusion 9 and Railo 3.1
        Hide
        Michael Offner
        added a comment -

        This was a issue in 3.1 not 3.2, there is also a ticket for that (search for "null"). Version 3.1 has interpreted "null" as a empty string, but "null" in a struct is always interpreted as not existing Key, interpret "null" as String "null" is Complete b..t.

        Show
        Michael Offner
        added a comment - This was a issue in 3.1 not 3.2, there is also a ticket for that (search for "null"). Version 3.1 has interpreted "null" as a empty string, but "null" in a struct is always interpreted as not existing Key, interpret "null" as String "null" is Complete b..t.
        Show
        Michael Offner
        added a comment - see https://issues.jboss.org/browse/RAILO-834

          People

          • Assignee:
            Michael Offner
            Reporter:
            Peter Pham
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: