This is EXACTLY what i was looking for. Thank you so much for this video. The way you explained every aspect and gave a reason for every decision, was very informative.
Thank you man, I was looking like crazy how to make these relationships and thanks to you I achieved it, thank you very much, you helped me a lot. Greetings from Colombia.
Oh, man. This is the best video for creating REST app with JPA I found on youtube. Previously, what you have in this video, I found in parts. It is a pity that youtube did not offer this video earlier. Keep up the good work!
Subscribed. One of the best resources to reach out to follow cleaner implementation and industry practices. Keep the great work, looking forward for content on microservices.
@@CodeForgeYT Bardzo się przydaje , szczególnie że miałem wcześniej mnóstwo problemów żeby znaleźć jakiś wartościowy film o springu. Tutaj wytłumaczyłeś prosto jak chłopu więc w końcu do mnie dotarło ! :D Keep going, nice channel !
@@CodeForgeYT no to ode mnie drugi :) fajny materiał, chociaż straszny mętlik się robi z tymi dto. Jakie są zagrożenia jeśli bez nich? Poza tym czy PlainCardDto jest konieczne jeśli mamy możliwość skorzystania z @JsonManagedReference i @JsonBackReference? Czy może są jakieś przeciwskazania do ich używania?
@Adam Bekisz Hey! Wielkie dzieki! Zagrozenia sa takie, ze bez nich w przypadku relacji dwukierunkowych przy serializacji jackson sie zapetli. Jesli nie chcesz stosowac DTO to spokojnie mozesz zastapic go encja z tymi wlasnie anotacjami. W zaleznosci od potrzeb mozna stosowac jedno lub drugie podejscie. DTO moim zdaniem jest o tyle fajne ze jest bardziej elastyczne w niektorych przypadkach, np. gdy potrzebujesz splaszczyc jakis obiekt. Proces mapowania DTO na encje i w druga strone mozna uproscic za pomoca biblioteczki mapstruct. Planuje w przyszlosci przygotowac wideo jak z niej korzysta. Pozdrawiam! Keep coding!
The way your created DTO is simple and awesome, Great, Thanks, keep up the good work. But can we have such methods on our entities, is it a good practice?
Hey! Great question. I think it is not considered a bad practice, but I think it would be better to have a mapper classes for entities where you can put mapper methods for each conversion. Alternative is to use library like mapstruct where you have to define interface and it will generate mappers for you, but it has its own pitfalls. Hope it helps. Keep coding!
Be careful with Data annotation from Lombok when you use it on entity, because it generate hash code and equals different than hash code used on jpa and can appear missunders when you want to use detached entities.
Hey here, i've trouble on the CartService.java at 1:10:15 , My problem is the getCart method appear in red with the message " Cannot resolve method getCart() " I don't understand wher's my problem, everything before work fine
Thank you! Very easy and helpful for my preparing to interview in English. Your pronunciation is very understandable for me. But your "generated" word pronunciation surprised me a little. It is close to my pronunciation of this word in Russian. Is English your native language?
As I think the author is from Poland, that's why his pronounciation is MUCH clearer than for example most of indian guys )) BTW great tutorial, thanks a lot!
the best course I have taken regarding spring. But I would like to know is it possible to directly assign a card to a tag without going through the controller?
your video is very helpful and congratulations for that, but why y don't define the deleteItem() like a void and delete the Item by deleteById(id) method ??
Jak to jest w koncu z tym DTO? Powinienem to stosowac zawsze, jesli nie to w jakich sytuacjach. Czy jezeli obiekt Dto ma w zasadzie takie same pola jak nasza encja nie moge po prostu wystawic naszej encji? Mozesz mi jeszcze raz wytlumaczyc po co zostal stworzony PlainCartDto? Nie dalo sie tego inaczej zrobic? Dodatkowe pytanie odnosnie ResponseEntity, w wielu poradnikach zwracany jest obiekt np Student, zgaduje ze raczej powinnismy korzystan z ResponeEntity by wyslac jeszcze dodatkowo poprawny status odpowiedzi? Pozdrawiam
Jesli chodzi o response entity to tak, lepiej obiekt opakowac niz wysylac go w surowej postaci. Nie trzeba robic Dto mozna zastosowac @JsonManagedReference, @JsonBackReference dla relacji dwukierunkowych. Generalnie jesli nie widzisz potrzeby hermetyzacji parametrow obiektow w dto, lub nie potrzebujesz innych parametrow w obiekcie niz te ktore sa w encji to spokojnie mozesz ich uzyc. Ja preferuje uzywanie dto.
Well, JpaRepository is the most complex one and it allows for operations on persistance context (it extends CrudRepository). Simply it wasn't necessary to use it here. We needed only CRUD operations so CrudRepository was good enough. Hope it helps. Keep coding!
This is EXACTLY what i was looking for. Thank you so much for this video. The way you explained every aspect and gave a reason for every decision, was very informative.
Thank you man, I was looking like crazy how to make these relationships and thanks to you I achieved it, thank you very much, you helped me a lot. Greetings from Colombia.
Oh, man. This is the best video for creating REST app with JPA I found on youtube. Previously, what you have in this video, I found in parts. It is a pity that youtube did not offer this video earlier. Keep up the good work!
Hey! Thanks for awesome feedback, glad you like the content! Keep coding! :D
Subscribed.
One of the best resources to reach out to follow cleaner implementation and industry practices.
Keep the great work, looking forward for content on microservices.
Wow, thanks for great feedback! Glad you like the content! Keep coding!
Thank You very much.
Excellent JPA playlist.
Easy to comprehend the underneath concept.
Kudos to your effort!!!
Hey! Thanks for the feedback. Happy to hear that you like it!
Thanks a lot, Great tutorial!! All worked just not the Swagger then I used Postman and everything was alright!!!
Liked. Subscribed.
One of the best resources out there!!!
Glad you like it! Thanks!
Thanks for this, very helpful to level up my understanding about springboot.
Awesome! Glad you like it
Thank you very much. Your video helped me a lot.
Just Subscribed. This tutorial absolutely helps me!! Thank you... thank you!
Thanks for the sub!
Świetne materiały! Szukałem takich tutków kupe czasu i w końcu znalazłem :) Po głosie od razu poznałem ,że z Polski :D
Hey! Super, ciesze sie, ze Ci sie przydalo! No i dzieki, za pozytywny feedback, to chyba pierwszy komentarz po polsku! :D
@@CodeForgeYT Bardzo się przydaje , szczególnie że miałem wcześniej mnóstwo problemów żeby znaleźć jakiś wartościowy film o springu. Tutaj wytłumaczyłeś prosto jak chłopu więc w końcu do mnie dotarło ! :D Keep going, nice channel !
@@CodeForgeYT no to ode mnie drugi :) fajny materiał, chociaż straszny mętlik się robi z tymi dto. Jakie są zagrożenia jeśli bez nich? Poza tym czy PlainCardDto jest konieczne jeśli mamy możliwość skorzystania z @JsonManagedReference i @JsonBackReference? Czy może są jakieś przeciwskazania do ich używania?
@Adam Bekisz Hey! Wielkie dzieki! Zagrozenia sa takie, ze bez nich w przypadku relacji dwukierunkowych przy serializacji jackson sie zapetli. Jesli nie chcesz stosowac DTO to spokojnie mozesz zastapic go encja z tymi wlasnie anotacjami. W zaleznosci od potrzeb mozna stosowac jedno lub drugie podejscie. DTO moim zdaniem jest o tyle fajne ze jest bardziej elastyczne w niektorych przypadkach, np. gdy potrzebujesz splaszczyc jakis obiekt. Proces mapowania DTO na encje i w druga strone mozna uproscic za pomoca biblioteczki mapstruct. Planuje w przyszlosci przygotowac wideo jak z niej korzysta. Pozdrawiam! Keep coding!
A jednak! A ja myślałem, że jakaś Albania/Rumunia.
It's a shame you have such a low ammount of views! Keep up the good work g!
Thanks, will do!
You saved my day. Thank you very much
Hey! Glad about it. Good rest of the day to you!
Good tutorial dude!
Thanks!
Goooooood job dude!
Thanks!
The way your created DTO is simple and awesome, Great, Thanks, keep up the good work. But can we have such methods on our entities, is it a good practice?
Hey! Great question. I think it is not considered a bad practice, but I think it would be better to have a mapper classes for entities where you can put mapper methods for each conversion. Alternative is to use library like mapstruct where you have to define interface and it will generate mappers for you, but it has its own pitfalls. Hope it helps. Keep coding!
Sure, got it...Thanks for the reply
Be careful with Data annotation from Lombok when you use it on entity, because it generate hash code and equals different than hash code used on jpa and can appear missunders when you want to use detached entities.
Hey! Thanks for sharing the knowledge, hope it will be useful for someone. Keep Coding!
Hey here, i've trouble on the CartService.java at 1:10:15 ,
My problem is the getCart method appear in red with the message " Cannot resolve method getCart() "
I don't understand wher's my problem, everything before work fine
Thank you! Very easy and helpful for my preparing to interview in English. Your pronunciation is very understandable for me.
But your "generated" word pronunciation surprised me a little.
It is close to my pronunciation of this word in Russian.
Is English your native language?
As I think the author is from Poland, that's why his pronounciation is MUCH clearer than for example most of indian guys )) BTW great tutorial, thanks a lot!
the best course I have taken regarding spring. But I would like to know is it possible to directly assign a card to a tag without going through the controller?
Glad you like it! What you mean by assinging card to a tag and by directly?
your video is very helpful and congratulations for that, but why y don't define the deleteItem() like a void and delete the Item by deleteById(id) method ??
Jak to jest w koncu z tym DTO? Powinienem to stosowac zawsze, jesli nie to w jakich sytuacjach. Czy jezeli obiekt Dto ma w zasadzie takie same pola jak nasza encja nie moge po prostu wystawic naszej encji?
Mozesz mi jeszcze raz wytlumaczyc po co zostal stworzony PlainCartDto? Nie dalo sie tego inaczej zrobic?
Dodatkowe pytanie odnosnie ResponseEntity, w wielu poradnikach zwracany jest obiekt np Student, zgaduje ze raczej powinnismy korzystan z ResponeEntity by wyslac jeszcze dodatkowo poprawny status odpowiedzi?
Pozdrawiam
Jesli chodzi o response entity to tak, lepiej obiekt opakowac niz wysylac go w surowej postaci.
Nie trzeba robic Dto mozna zastosowac @JsonManagedReference, @JsonBackReference dla relacji dwukierunkowych.
Generalnie jesli nie widzisz potrzeby hermetyzacji parametrow obiektow w dto, lub nie potrzebujesz innych parametrow w obiekcie niz te ktore sa w encji to spokojnie mozesz ich uzyc. Ja preferuje uzywanie dto.
Hi sir, for me removeItemFromCart() is not functioning. It is not deleting the item from cart no change in the cart items plz help.
Why did you not use JpaRepository instead of Crud one?
Well, JpaRepository is the most complex one and it allows for operations on persistance context (it extends CrudRepository). Simply it wasn't necessary to use it here. We needed only CRUD operations so CrudRepository was good enough. Hope it helps. Keep coding!
@@CodeForgeYT Good point thanks keep coding too
: )