Jackson JSON Processor
  1. Jackson JSON Processor
  2. JACKSON-558

DeserializationConfig.Feature - UNWRAP_ROOT_VALUE implementation request

    Details

    • Type: New Feature New Feature
    • Status: Resolved Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.7.6
    • Fix Version/s: None
    • Component/s: JsonParser
    • Labels:
      None
    • Number of attachments :
      0

      Description

      I was checking out SerializationConfig.Feature.WRAP_ROOT_VALUE setting and although the Javadoc says it's not implemented, it works on 1.7.x
      So then I was trying the same setting on DeserializationConfig.Feature (the javadoc/source says that it's not implemented, and probably the name should also change to UNWRAP_ROOT_VALUE, on the Deserialization side)

      Could we have this in the next possible minor/patch release, maybe?

      Thanks!
      Anand

      PS: A discussion here http://stackoverflow.com/questions/5728276/jackson-json-top-level-segment-inclusion , prompted me to create this JIRA.

        Activity

        Hide
        Tatu Saloranta added a comment -

        Right, javadoc for SerializationConfig was out of date.

        This can be considered for the next minor release; which given timing will be 1.9.

        Show
        Tatu Saloranta added a comment - Right, javadoc for SerializationConfig was out of date. This can be considered for the next minor release; which given timing will be 1.9.
        Hide
        Dusan Katona added a comment -

        Would it be possible to release it as a patch before 1.9? We really need this feature for deserialization of JAXB annotated classes. Thank you.

        Show
        Dusan Katona added a comment - Would it be possible to release it as a patch before 1.9? We really need this feature for deserialization of JAXB annotated classes. Thank you.
        Hide
        Tatu Saloranta added a comment -

        No changes to API can be done in a patch release; patches are just for bug fixes.
        So it needs to be in 1.9.

        It could be released in 1.9 snapshot build (or built locally from trunk); trunk is for 1.9 development so the new feature can be available before official build is done.

        Most importantly of course someone has to implement the feature first.

        Show
        Tatu Saloranta added a comment - No changes to API can be done in a patch release; patches are just for bug fixes. So it needs to be in 1.9. It could be released in 1.9 snapshot build (or built locally from trunk); trunk is for 1.9 development so the new feature can be available before official build is done. Most importantly of course someone has to implement the feature first.
        Hide
        Tatu Saloranta added a comment -

        Implemented.

        Show
        Tatu Saloranta added a comment - Implemented.

          People

          • Assignee:
            Tatu Saloranta
            Reporter:
            Anand H
          • Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: