This is the how JAX-RS REST API is implemented from Spring framework . It is very similar to javaEE implementation https://www.baeldung.com/jersey-rest-api-with-spring
HQL & JPAQuery for Springboot => https://drive.google.com/drive/u/1/folders/18KA0A0EKYmn6Z7auazNquPDaweqPQvHI https://www.baeldung.com/jpa-join-types (only if we want to write join query, but in HQL no need of using join key word , if we can correctly implement the mapping classes ) Native SQL for Springboot => https://drive.google.com/drive/u/1/folders/17vdDhEXBKtbWpTkYUy5UcF_n_r2G-YDy projects => https://drive.google.com/drive/folders/14x_9TeE5SZq6ECZqCmoBaGTgOUSssuqm?usp=sharing We can write plan SQL Query in hibernate using session.createSQLQuery(sqlSearch); Eg-:: String sqlSearch = SQLVarList.MSSQL_DEVICEOPERATIONREPORT_SQL2 + where + orderBy; Query querySearch = session.createSQLQuery(sqlSearch); querySearch = setD...
SN : https://drive.google.com/file/d/1qBOFXGed_4v01WX8wG73mMF0yeJ0Putu/view?usp=drive_link AWS LB & Route53 https://towardsaws.com/network-in-aws-route53-vpc-bbf18a2ab054#:~:text=Route%2053%20is%20used%20for,user's%20location%20or%20other%20criteria. AWS IAM https://awsfundamentals.com/blog/aws-iam-roles-terms-concepts-and-examples#heading-aws-identity-center-and-federation In AWS, *users* and *roles* are two distinct concepts that serve different purposes in managing access and identity. AWS User - *Definition*: An AWS user is an entity that represents a person or application that interacts with AWS resources. - *Characteristics*: - Users have long-term credenti...
This is the how JAX-RS REST API is implemented from Spring framework . It is very similar to javaEE implementation
ReplyDeletehttps://www.baeldung.com/jersey-rest-api-with-spring
Encapsulation.. public getters , public setters and private attributes are used to validate attribute before adding it object
ReplyDelete