OneToMany mapping not working in the Controller crud Spring Boot Rest API












0















I don't know how to solve the 500 status response by the api. I am testing with Postman.



The request



{
"nome": "Ciencia da Computação",
"totalCreditos": 2333,
"professor": {
"id": 2,
"matricula": 0,
"nome": "José da silva"
}
}


How do I implement One to many relationship and expose the api the correct way for CRUD operation.
I'm getting a 500 error.
I don't know if I need to change the Controller functions



CursoController.java



@CrossOrigin(origins = "*")
@RestController
@RequestMapping({"/api/curso"})
public class CursoController {
@Autowired
private CursoService cursoService;
private ProfessorService professorService;

@PostMapping
public Curso create(@RequestBody Curso curso){
return cursoService.create(curso);
}

@GetMapping(path = {"/{id}"})
public Curso findOne(@PathVariable("id") int id){
return cursoService.findById(id);
}

@PutMapping
public Curso update(@RequestBody Curso Curso){
return cursoService.update(Curso);
}

@DeleteMapping(path ={"/{id}"})
public Curso delete(@PathVariable("id") int id) {
return cursoService.delete(id);
}

@GetMapping
public List findAll(){
return cursoService.findAll();
}
}


Curso.java



@Entity
@Table(name = "curso")
public class Curso implements Serializable {
@Id
@Column
@GeneratedValue(strategy = GenerationType.IDENTITY)
private int id;
@Column
@GeneratedValue(strategy = GenerationType.AUTO)
private Long codigo;
@Column
private Long totalCreditos;

@Column
private String nome;

@ManyToOne(fetch = FetchType.LAZY, optional = false, cascade =
CascadeType.PERSIST)
@JoinColumn(name = "professor_id", nullable = false)
@OnDelete(action = OnDeleteAction.CASCADE)
@JsonIgnore
@JsonManagedReference
private Professor professor;


}









share|improve this question























  • also can you share Professor entity class here?also share serviceimpl class as well.

    – GauravRai1512
    Nov 21 '18 at 1:41













  • can you share curso pojo class?

    – GauravRai1512
    Nov 21 '18 at 1:55
















0















I don't know how to solve the 500 status response by the api. I am testing with Postman.



The request



{
"nome": "Ciencia da Computação",
"totalCreditos": 2333,
"professor": {
"id": 2,
"matricula": 0,
"nome": "José da silva"
}
}


How do I implement One to many relationship and expose the api the correct way for CRUD operation.
I'm getting a 500 error.
I don't know if I need to change the Controller functions



CursoController.java



@CrossOrigin(origins = "*")
@RestController
@RequestMapping({"/api/curso"})
public class CursoController {
@Autowired
private CursoService cursoService;
private ProfessorService professorService;

@PostMapping
public Curso create(@RequestBody Curso curso){
return cursoService.create(curso);
}

@GetMapping(path = {"/{id}"})
public Curso findOne(@PathVariable("id") int id){
return cursoService.findById(id);
}

@PutMapping
public Curso update(@RequestBody Curso Curso){
return cursoService.update(Curso);
}

@DeleteMapping(path ={"/{id}"})
public Curso delete(@PathVariable("id") int id) {
return cursoService.delete(id);
}

@GetMapping
public List findAll(){
return cursoService.findAll();
}
}


Curso.java



@Entity
@Table(name = "curso")
public class Curso implements Serializable {
@Id
@Column
@GeneratedValue(strategy = GenerationType.IDENTITY)
private int id;
@Column
@GeneratedValue(strategy = GenerationType.AUTO)
private Long codigo;
@Column
private Long totalCreditos;

@Column
private String nome;

@ManyToOne(fetch = FetchType.LAZY, optional = false, cascade =
CascadeType.PERSIST)
@JoinColumn(name = "professor_id", nullable = false)
@OnDelete(action = OnDeleteAction.CASCADE)
@JsonIgnore
@JsonManagedReference
private Professor professor;


}









share|improve this question























  • also can you share Professor entity class here?also share serviceimpl class as well.

    – GauravRai1512
    Nov 21 '18 at 1:41













  • can you share curso pojo class?

    – GauravRai1512
    Nov 21 '18 at 1:55














0












0








0








I don't know how to solve the 500 status response by the api. I am testing with Postman.



The request



{
"nome": "Ciencia da Computação",
"totalCreditos": 2333,
"professor": {
"id": 2,
"matricula": 0,
"nome": "José da silva"
}
}


How do I implement One to many relationship and expose the api the correct way for CRUD operation.
I'm getting a 500 error.
I don't know if I need to change the Controller functions



CursoController.java



@CrossOrigin(origins = "*")
@RestController
@RequestMapping({"/api/curso"})
public class CursoController {
@Autowired
private CursoService cursoService;
private ProfessorService professorService;

@PostMapping
public Curso create(@RequestBody Curso curso){
return cursoService.create(curso);
}

@GetMapping(path = {"/{id}"})
public Curso findOne(@PathVariable("id") int id){
return cursoService.findById(id);
}

@PutMapping
public Curso update(@RequestBody Curso Curso){
return cursoService.update(Curso);
}

@DeleteMapping(path ={"/{id}"})
public Curso delete(@PathVariable("id") int id) {
return cursoService.delete(id);
}

@GetMapping
public List findAll(){
return cursoService.findAll();
}
}


Curso.java



@Entity
@Table(name = "curso")
public class Curso implements Serializable {
@Id
@Column
@GeneratedValue(strategy = GenerationType.IDENTITY)
private int id;
@Column
@GeneratedValue(strategy = GenerationType.AUTO)
private Long codigo;
@Column
private Long totalCreditos;

@Column
private String nome;

@ManyToOne(fetch = FetchType.LAZY, optional = false, cascade =
CascadeType.PERSIST)
@JoinColumn(name = "professor_id", nullable = false)
@OnDelete(action = OnDeleteAction.CASCADE)
@JsonIgnore
@JsonManagedReference
private Professor professor;


}









share|improve this question














I don't know how to solve the 500 status response by the api. I am testing with Postman.



The request



{
"nome": "Ciencia da Computação",
"totalCreditos": 2333,
"professor": {
"id": 2,
"matricula": 0,
"nome": "José da silva"
}
}


How do I implement One to many relationship and expose the api the correct way for CRUD operation.
I'm getting a 500 error.
I don't know if I need to change the Controller functions



CursoController.java



@CrossOrigin(origins = "*")
@RestController
@RequestMapping({"/api/curso"})
public class CursoController {
@Autowired
private CursoService cursoService;
private ProfessorService professorService;

@PostMapping
public Curso create(@RequestBody Curso curso){
return cursoService.create(curso);
}

@GetMapping(path = {"/{id}"})
public Curso findOne(@PathVariable("id") int id){
return cursoService.findById(id);
}

@PutMapping
public Curso update(@RequestBody Curso Curso){
return cursoService.update(Curso);
}

@DeleteMapping(path ={"/{id}"})
public Curso delete(@PathVariable("id") int id) {
return cursoService.delete(id);
}

@GetMapping
public List findAll(){
return cursoService.findAll();
}
}


Curso.java



@Entity
@Table(name = "curso")
public class Curso implements Serializable {
@Id
@Column
@GeneratedValue(strategy = GenerationType.IDENTITY)
private int id;
@Column
@GeneratedValue(strategy = GenerationType.AUTO)
private Long codigo;
@Column
private Long totalCreditos;

@Column
private String nome;

@ManyToOne(fetch = FetchType.LAZY, optional = false, cascade =
CascadeType.PERSIST)
@JoinColumn(name = "professor_id", nullable = false)
@OnDelete(action = OnDeleteAction.CASCADE)
@JsonIgnore
@JsonManagedReference
private Professor professor;


}






java rest maven api spring-boot






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 1:31









Rafael ÁquilaRafael Áquila

82




82













  • also can you share Professor entity class here?also share serviceimpl class as well.

    – GauravRai1512
    Nov 21 '18 at 1:41













  • can you share curso pojo class?

    – GauravRai1512
    Nov 21 '18 at 1:55



















  • also can you share Professor entity class here?also share serviceimpl class as well.

    – GauravRai1512
    Nov 21 '18 at 1:41













  • can you share curso pojo class?

    – GauravRai1512
    Nov 21 '18 at 1:55

















also can you share Professor entity class here?also share serviceimpl class as well.

– GauravRai1512
Nov 21 '18 at 1:41







also can you share Professor entity class here?also share serviceimpl class as well.

– GauravRai1512
Nov 21 '18 at 1:41















can you share curso pojo class?

– GauravRai1512
Nov 21 '18 at 1:55





can you share curso pojo class?

– GauravRai1512
Nov 21 '18 at 1:55












2 Answers
2






active

oldest

votes


















0














Can you use CascadeType.ALL whitch Cascade all operations (PERSIST,MERGE,REMOVE,REFRESH,DETACH).
For more details you can take a look here






share|improve this answer































    0














    you should never use CascadeType.ALL on @ManyToOne since entity state transitions should propagate from Parent entities to Child ones.



    Remove



    (fetch = FetchType.LAZY, optional = false, cascade = 
    CascadeType.PERSIST)


    from



    @ManyToOne(fetch = FetchType.LAZY, optional = false, cascade = 
    CascadeType.PERSIST)


    and add it in



     @OneToMany(fetch = FetchType.LAZY, optional = false, cascade = 
    CascadeType.PERSIST)


    side.



    Explanation :



    As vladmihalcea explained in this article and in his book, High-Performance Java Persistence, you should never use CascadeType.ALL on @ManyToOne since entity state transitions should propagate from Parent entities to Child ones.



    The @ManyToOne side is always the Child association since it should map the underlying FK.



    Therefore, move the CascadeType.ALL from the @ManyToOne association to the @OneToMany which should use the mappedBy attribute since it's the most efficient one-to-many mapping.
    `






    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%2f53404082%2fonetomany-mapping-not-working-in-the-controller-crud-spring-boot-rest-api%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      Can you use CascadeType.ALL whitch Cascade all operations (PERSIST,MERGE,REMOVE,REFRESH,DETACH).
      For more details you can take a look here






      share|improve this answer




























        0














        Can you use CascadeType.ALL whitch Cascade all operations (PERSIST,MERGE,REMOVE,REFRESH,DETACH).
        For more details you can take a look here






        share|improve this answer


























          0












          0








          0







          Can you use CascadeType.ALL whitch Cascade all operations (PERSIST,MERGE,REMOVE,REFRESH,DETACH).
          For more details you can take a look here






          share|improve this answer













          Can you use CascadeType.ALL whitch Cascade all operations (PERSIST,MERGE,REMOVE,REFRESH,DETACH).
          For more details you can take a look here







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 21 '18 at 2:07









          TinyOSTinyOS

          92311029




          92311029

























              0














              you should never use CascadeType.ALL on @ManyToOne since entity state transitions should propagate from Parent entities to Child ones.



              Remove



              (fetch = FetchType.LAZY, optional = false, cascade = 
              CascadeType.PERSIST)


              from



              @ManyToOne(fetch = FetchType.LAZY, optional = false, cascade = 
              CascadeType.PERSIST)


              and add it in



               @OneToMany(fetch = FetchType.LAZY, optional = false, cascade = 
              CascadeType.PERSIST)


              side.



              Explanation :



              As vladmihalcea explained in this article and in his book, High-Performance Java Persistence, you should never use CascadeType.ALL on @ManyToOne since entity state transitions should propagate from Parent entities to Child ones.



              The @ManyToOne side is always the Child association since it should map the underlying FK.



              Therefore, move the CascadeType.ALL from the @ManyToOne association to the @OneToMany which should use the mappedBy attribute since it's the most efficient one-to-many mapping.
              `






              share|improve this answer




























                0














                you should never use CascadeType.ALL on @ManyToOne since entity state transitions should propagate from Parent entities to Child ones.



                Remove



                (fetch = FetchType.LAZY, optional = false, cascade = 
                CascadeType.PERSIST)


                from



                @ManyToOne(fetch = FetchType.LAZY, optional = false, cascade = 
                CascadeType.PERSIST)


                and add it in



                 @OneToMany(fetch = FetchType.LAZY, optional = false, cascade = 
                CascadeType.PERSIST)


                side.



                Explanation :



                As vladmihalcea explained in this article and in his book, High-Performance Java Persistence, you should never use CascadeType.ALL on @ManyToOne since entity state transitions should propagate from Parent entities to Child ones.



                The @ManyToOne side is always the Child association since it should map the underlying FK.



                Therefore, move the CascadeType.ALL from the @ManyToOne association to the @OneToMany which should use the mappedBy attribute since it's the most efficient one-to-many mapping.
                `






                share|improve this answer


























                  0












                  0








                  0







                  you should never use CascadeType.ALL on @ManyToOne since entity state transitions should propagate from Parent entities to Child ones.



                  Remove



                  (fetch = FetchType.LAZY, optional = false, cascade = 
                  CascadeType.PERSIST)


                  from



                  @ManyToOne(fetch = FetchType.LAZY, optional = false, cascade = 
                  CascadeType.PERSIST)


                  and add it in



                   @OneToMany(fetch = FetchType.LAZY, optional = false, cascade = 
                  CascadeType.PERSIST)


                  side.



                  Explanation :



                  As vladmihalcea explained in this article and in his book, High-Performance Java Persistence, you should never use CascadeType.ALL on @ManyToOne since entity state transitions should propagate from Parent entities to Child ones.



                  The @ManyToOne side is always the Child association since it should map the underlying FK.



                  Therefore, move the CascadeType.ALL from the @ManyToOne association to the @OneToMany which should use the mappedBy attribute since it's the most efficient one-to-many mapping.
                  `






                  share|improve this answer













                  you should never use CascadeType.ALL on @ManyToOne since entity state transitions should propagate from Parent entities to Child ones.



                  Remove



                  (fetch = FetchType.LAZY, optional = false, cascade = 
                  CascadeType.PERSIST)


                  from



                  @ManyToOne(fetch = FetchType.LAZY, optional = false, cascade = 
                  CascadeType.PERSIST)


                  and add it in



                   @OneToMany(fetch = FetchType.LAZY, optional = false, cascade = 
                  CascadeType.PERSIST)


                  side.



                  Explanation :



                  As vladmihalcea explained in this article and in his book, High-Performance Java Persistence, you should never use CascadeType.ALL on @ManyToOne since entity state transitions should propagate from Parent entities to Child ones.



                  The @ManyToOne side is always the Child association since it should map the underlying FK.



                  Therefore, move the CascadeType.ALL from the @ManyToOne association to the @OneToMany which should use the mappedBy attribute since it's the most efficient one-to-many mapping.
                  `







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 21 '18 at 4:35









                  AlienAlien

                  4,95331026




                  4,95331026






























                      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%2f53404082%2fonetomany-mapping-not-working-in-the-controller-crud-spring-boot-rest-api%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

                      MongoDB - Not Authorized To Execute Command

                      How to fix TextFormField cause rebuild widget in Flutter

                      in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith