Видео

Can we call procedure with in and out param?

Great content. Lucid explanation.

You’ve done a better job then my teachers and the textbooks 😊😊

I love you so much. I dont know how much i searched for my problem and how many people I saw searching for the same solution, but nobody mentioned the equals method when converting the objects. That fixed everything for me. Thank you sooooo much! Very good and useful Video!

You've used a fun example - unfortunately, the shortened URL links don't work. Can you correct them?

nice explanation. 2024 an i am about to start learning about it.. thanks

Thank you

Good Tutorial, Thank you from Italy

Great video!

Hello. Thanks for the video. From my experience, the migration folder should be db/migration, but showed on IDE as db.migration. If we use a folder named db.migration, flyway migration script won't be executed.

great content 💪🚀

Well explained

Great explanation. Thanks for sharing this.

شرح بسيط ورائع❤❤

Great video, thanks! Other courses I've taken have grouped all the Controllers in a package, the Repositories in another package, Models in a package etc. I like the way you group your classes. Is this just a personal preference (for locating them easier) or another reason?

As a backend dev who is trying to get into full-stack, thank you so much for the video. The clearest expalanation I was able to find online for the HTML part :)

Perfect

Very good demonstration. 😀

Thank you very much! Your video was very helpful.

This is honestly the best sql tutorial I’ve come accross - nice and succinct and straight forward , thank you!😊

This is a really great tutorial! Thank you!

great content, great explanation, keep going please 🙏

We're using void statements here. Why should we use a reference parameter and a void method, when we can return a function using i.e. an int method?

Thank you very Much

thanks, a lot ❤

So glad I came across this tutorial and thank you. I find your detailed explanation very easy to understand. Keep it up please.

thanks

super helpful, thank you

Very good

you are amazing thank you

thks bro you are genius love you bitch

This is a real gem Thank you sir !

amazing tutorials!

Best explanation ever! Thank you!

i understand how a value parameter works now thank you, but i'm confused on what is the point of using a value parameter? Why use a value parameter is my question?

Can i get all source code about architectural pattern?

I hate you eww

4:38 WordCountBean 5:56

0:49 idea of table table: *fixed number of columns, but it will have one row per object in the collection* => a variable sized table 0:59 in the html lib namespace 1:09 need 2 elements - h:dataTable and h:column

Thank you very much geat explanation

0:19

21:05 managing entities - EntityManager 21:56 Container-managed EntityManager 22:32 how to inject EntityManager into a component 22:55 meaning: when your class got this annotation, the *container* will detect the annotation and will then look for an existing EntityManager that can be used 23:19 JTA allows us to make use of transactions to make sure the the database and data models are properly synchronized 24:27 we should *always use the container-managed EntityManager* along with the JTA transactions 24:34 life-cycle of entity object 24:57 *new* - *no persistent identity* yet 25:36 *managed* - 25:47 this object is associated with a row in the (db) table, 25:52 in another word, this row will be inserted (into db) 26:34 27:15 *detached* 28:06 EntityManager.persist 28:52

0:35 annotations 1:56 dependency injection 3:07 JNDI 3:39 *resources that can be injected* 3:42 SessionContext, DataSource 3:45 EntityManager 4:02 example: *@Resource* 4:13 4:26 JPA 5:16 Entity - 5:21 a POJO 5:56 it provides for *standardized object-relational mapping* 7:14 named queries 8:32 Key features of JPA 8:39 Detached entities 9:23 EntityManager - 9:30 perform CRUD operations on entities 9:38 persistence units 10:05 properties 10:37 identify persistence storage of the managed entities 10:54 identify the *transaction type* 11:07

18:58 a good software engineering principle - 19:02 *only talk to your immediate neighbor* 19:33 minimize the connections between one class and another

1:13 motivation of these design patterns 1:16 mismatch of paradigms - 1:26 we are using *oo* and *relational database* and the two don't match 1:45 thus far, we have embedded SQL into the managed beans and their helper POJOs 1:52 makes maintenance awkward 1:54 SQL code cannot be easily found 2:00 putting all SQL statements into one interface does not remove the lack of oo structure 2:41 solution - design patterns 3:42 Table Data Gateway 4:19 the previous solution with USDP 4:34 *UML example demo of using table gateway* 6:05 *UML example demo of using view gateway* 6:32 just one CustomerGateway class - 6:47 the SQL will query not the just Customer but also the Discount table using a *join* 7:18 code example 8:33 CustomerGateway.find(int customerID)

11:36 row data gateway 13:10 find() can be held as static 13:32 still no business logic in the methods 14:03 UML class dia - possibility 1 14:14 the find method has become static 14:17 customer fields - represent the fields in the database 14:49 possibility 2 - continue to use DTOs 15:50 active record 16:11 the active record is a combination of row data gateway plus domain logic 16:26 also have the business logic 17:50 class diagram

8:01 Use case model

5:14

4:08

8:09