Spring Data Rest POST response different from GET response












1















On my Spring Data Rest project I have a Competition entity that references an GeoLocation entity:



public class Competition {
@Id
private String uname;

[...]

@NotNull
@OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.LAZY)
private GeoLocation geoLocation;
}

public class GeoLocation {
@Id private Long id;
private Double latitude;
private Double longitude;
}


Since every Competition must have a GeoLocation defined, the Competition entity handles the creation via cascade. When creating a new Competition entity via POST, I get the following response:



{
"uname": "Some Competition",
"geoLocation": {
[content of geoLocation]
},
"_links": {
[...]
}
}


But when I call the newly created competition, the content of the GeoLocation will be wrapped in a content field.



{
"uname": "Some Competition",
"geoLocation": {
"content": {
[content of geoLocation]
}
},
"_links": {
[...]
}
}


I would expect that both requests would deliver the same response?










share|improve this question























  • Possibly same issue as I asked about here: stackoverflow.com/questions/42395831/…

    – Alan Hay
    Nov 26 '18 at 8:35











  • @AlanHay that looks almost identical, thank you.

    – Sebastian Ullrich
    Nov 26 '18 at 9:45











  • If so, making your relationship eager would probably solve.

    – Alan Hay
    Nov 26 '18 at 9:57











  • You're right again @AlanHay. Changing to Eager solved this issue.

    – Sebastian Ullrich
    Nov 26 '18 at 20:23


















1















On my Spring Data Rest project I have a Competition entity that references an GeoLocation entity:



public class Competition {
@Id
private String uname;

[...]

@NotNull
@OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.LAZY)
private GeoLocation geoLocation;
}

public class GeoLocation {
@Id private Long id;
private Double latitude;
private Double longitude;
}


Since every Competition must have a GeoLocation defined, the Competition entity handles the creation via cascade. When creating a new Competition entity via POST, I get the following response:



{
"uname": "Some Competition",
"geoLocation": {
[content of geoLocation]
},
"_links": {
[...]
}
}


But when I call the newly created competition, the content of the GeoLocation will be wrapped in a content field.



{
"uname": "Some Competition",
"geoLocation": {
"content": {
[content of geoLocation]
}
},
"_links": {
[...]
}
}


I would expect that both requests would deliver the same response?










share|improve this question























  • Possibly same issue as I asked about here: stackoverflow.com/questions/42395831/…

    – Alan Hay
    Nov 26 '18 at 8:35











  • @AlanHay that looks almost identical, thank you.

    – Sebastian Ullrich
    Nov 26 '18 at 9:45











  • If so, making your relationship eager would probably solve.

    – Alan Hay
    Nov 26 '18 at 9:57











  • You're right again @AlanHay. Changing to Eager solved this issue.

    – Sebastian Ullrich
    Nov 26 '18 at 20:23
















1












1








1








On my Spring Data Rest project I have a Competition entity that references an GeoLocation entity:



public class Competition {
@Id
private String uname;

[...]

@NotNull
@OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.LAZY)
private GeoLocation geoLocation;
}

public class GeoLocation {
@Id private Long id;
private Double latitude;
private Double longitude;
}


Since every Competition must have a GeoLocation defined, the Competition entity handles the creation via cascade. When creating a new Competition entity via POST, I get the following response:



{
"uname": "Some Competition",
"geoLocation": {
[content of geoLocation]
},
"_links": {
[...]
}
}


But when I call the newly created competition, the content of the GeoLocation will be wrapped in a content field.



{
"uname": "Some Competition",
"geoLocation": {
"content": {
[content of geoLocation]
}
},
"_links": {
[...]
}
}


I would expect that both requests would deliver the same response?










share|improve this question














On my Spring Data Rest project I have a Competition entity that references an GeoLocation entity:



public class Competition {
@Id
private String uname;

[...]

@NotNull
@OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.LAZY)
private GeoLocation geoLocation;
}

public class GeoLocation {
@Id private Long id;
private Double latitude;
private Double longitude;
}


Since every Competition must have a GeoLocation defined, the Competition entity handles the creation via cascade. When creating a new Competition entity via POST, I get the following response:



{
"uname": "Some Competition",
"geoLocation": {
[content of geoLocation]
},
"_links": {
[...]
}
}


But when I call the newly created competition, the content of the GeoLocation will be wrapped in a content field.



{
"uname": "Some Competition",
"geoLocation": {
"content": {
[content of geoLocation]
}
},
"_links": {
[...]
}
}


I would expect that both requests would deliver the same response?







spring hibernate jpa spring-data-rest






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 25 '18 at 22:41









Sebastian UllrichSebastian Ullrich

31219




31219













  • Possibly same issue as I asked about here: stackoverflow.com/questions/42395831/…

    – Alan Hay
    Nov 26 '18 at 8:35











  • @AlanHay that looks almost identical, thank you.

    – Sebastian Ullrich
    Nov 26 '18 at 9:45











  • If so, making your relationship eager would probably solve.

    – Alan Hay
    Nov 26 '18 at 9:57











  • You're right again @AlanHay. Changing to Eager solved this issue.

    – Sebastian Ullrich
    Nov 26 '18 at 20:23





















  • Possibly same issue as I asked about here: stackoverflow.com/questions/42395831/…

    – Alan Hay
    Nov 26 '18 at 8:35











  • @AlanHay that looks almost identical, thank you.

    – Sebastian Ullrich
    Nov 26 '18 at 9:45











  • If so, making your relationship eager would probably solve.

    – Alan Hay
    Nov 26 '18 at 9:57











  • You're right again @AlanHay. Changing to Eager solved this issue.

    – Sebastian Ullrich
    Nov 26 '18 at 20:23



















Possibly same issue as I asked about here: stackoverflow.com/questions/42395831/…

– Alan Hay
Nov 26 '18 at 8:35





Possibly same issue as I asked about here: stackoverflow.com/questions/42395831/…

– Alan Hay
Nov 26 '18 at 8:35













@AlanHay that looks almost identical, thank you.

– Sebastian Ullrich
Nov 26 '18 at 9:45





@AlanHay that looks almost identical, thank you.

– Sebastian Ullrich
Nov 26 '18 at 9:45













If so, making your relationship eager would probably solve.

– Alan Hay
Nov 26 '18 at 9:57





If so, making your relationship eager would probably solve.

– Alan Hay
Nov 26 '18 at 9:57













You're right again @AlanHay. Changing to Eager solved this issue.

– Sebastian Ullrich
Nov 26 '18 at 20:23







You're right again @AlanHay. Changing to Eager solved this issue.

– Sebastian Ullrich
Nov 26 '18 at 20:23














1 Answer
1






active

oldest

votes


















1














@JsonUnwrapped solved this issue for me:



public class Competition {
@Id
private String uname;

[...]

@NotNull
@JsonUnwrapped
@OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.LAZY)
private GeoLocation geoLocation;
}





share|improve this answer























    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%2f53472735%2fspring-data-rest-post-response-different-from-get-response%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









    1














    @JsonUnwrapped solved this issue for me:



    public class Competition {
    @Id
    private String uname;

    [...]

    @NotNull
    @JsonUnwrapped
    @OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.LAZY)
    private GeoLocation geoLocation;
    }





    share|improve this answer




























      1














      @JsonUnwrapped solved this issue for me:



      public class Competition {
      @Id
      private String uname;

      [...]

      @NotNull
      @JsonUnwrapped
      @OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.LAZY)
      private GeoLocation geoLocation;
      }





      share|improve this answer


























        1












        1








        1







        @JsonUnwrapped solved this issue for me:



        public class Competition {
        @Id
        private String uname;

        [...]

        @NotNull
        @JsonUnwrapped
        @OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.LAZY)
        private GeoLocation geoLocation;
        }





        share|improve this answer













        @JsonUnwrapped solved this issue for me:



        public class Competition {
        @Id
        private String uname;

        [...]

        @NotNull
        @JsonUnwrapped
        @OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, fetch = FetchType.LAZY)
        private GeoLocation geoLocation;
        }






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 4 '18 at 23:06









        Sebastian UllrichSebastian Ullrich

        31219




        31219
































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53472735%2fspring-data-rest-post-response-different-from-get-response%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

            404 Error Contact Form 7 ajax form submitting

            How to know if a Active Directory user can login interactively

            Refactoring coordinates for Minecraft Pi buildings written in Python