JSR 303 Validation

JSR 303 Bean Validation is the specification of the Java API for JavaBean validation in Java EE and Java SE. Simply put it provides an easy way of ensuring that the properties of your JavaBean(s) have the right values in them. Prior to JSR 303, we would required to handle the validation using if-else statements. In this POST we will do following.

We will create customer bean, add various JSR 303 validation annotation to its.
Will create REST endpoint where in request body will be customer bean.
Around aspect will be created which will validate the beans before controller gets called.

Java Code

Customer.java

RestController

DataValidator

DataValidator Aspect

Dependencies

Here we have provided hibernate-validator as implementation provider for JSR303, you guys can use other implementation provider also.

Output using curl

curl -i -X POST -H "Content-Type:application/json" http://localhost:8082/cust -d '{"fName":"12345", "lName":"1"}'

GIT Url

Cheers – Happy learning 🙂
Ketan Gote

Comments

Centralized configuration using Spring Cloud Config

In this blog we will be focusing on centralized configuration using Spring Cloud Config project. For single standalone application we can keep all required configuration bundle with application itself. However, when we have more than one application, say in a microservice architecture, a better alternative would be to manage the configurations centrally. With the Config Server we have a central place to manage external properties for applications with support for different environments. Configuration files in several formats like YAML or properties are added to a Git repository. Features Spring Cloud Config Server features: HTTP, resource-based API for external configuration (name-value pairs, or equivalent YAML content) Encrypt and decrypt property values (symmetric or asymmetric) Embeddable easily in a Spring Boot application using @EnableConfigServer Config Client features (for Spring applications): Bind to the Config Server and initialize...

Function Point Analysis : ISO/IEC 20926:2009

This blog focuses on explaining the Function Point calculations. Software Sizing Background Function Point Rules for Counting FP Deep Dive - Function Point Analysis Case Study General Software Characteristics Details History - Measurement Methodologies Lines of Code (Oldest) Use case based Software Sizing IPFUG Function Point Analysis (ISO) Need for Software Sizing. Estimation and Budgeting Phasing Development Work Prioritization of Work Monitoring the Progress Bidding for Projects Allocating Testing Resources To measure and Manage Productivity Risk Assessment Software Asset Valuation CMMi Level 2 and 3 require that a valid sizing method be used. Software Sizing - Lines of Code The easiest and historically the most common method in Sizing Software project has been counting the number of lines of code and / or the number of screens. Advantages Automation of the counting process can be done Intuitive as the measurements are easily u...

CRUD in MongoDB & Spring Data

Now, since we have already been introduced to mongo and its server is setup. We shall now move on to performing basic CRUD operations. Lets take a use case example of ‘Company’ database that stores employee information. We wish to store employee name, email address, age and multiple addresses. Traditionally in RDBMS we would create an Employee table and Address Table having foreign key reference to ‘employee id ‘ Incase of NoSQL, we will be creating Employee documnet which will have store employee information like name, email, age and an array of employes address. Following is a snippet of the schema defined { "name" : "", "email" : "", "age" : “”, "address" : [ ... ] } Thus to begin with, we will first define the entities. We have employee as an aggregate root entity that stores list of address having 1-M relatioship. Address Entity is represend as @Embeddable as it is embaded in another aggregate root entity. Employee is...

MetaMagic Developer Blogs

Search This Blog