Spring MVC Formatter: First of all, Why do we need a formatter? Well, The importance of a formatter comes when our app requires some special formartting. Imagine a phone number like 91-213132131212, which needs to be bind with a Phone object having a string country code, phone number properties.
A scenario like this needs to be handled by the developer by using an interface called Formatter.
When The user submits a form, all the input we get in string format. Spring framework internally converts all the values to a required data type.
Now, The problem comes when the auto data binding fails. Think about the phone number example, Where the user gives the phone input as the String and, We need to convert the string to a phone object.
Here, We need to bind the data manually by using the Spring Formatter interface.
We will have a deep dive into this concept here in this video.
To Use the Formatter interface, We need to understand three different interfaces.
Formatter Interface
Printer Interface
Parser Interface
The Printer and the Parser Interface have the print() and the parse() methods, respectively.
The print() helps for displaying the object, whereas the parse helps for the conversion of an object.
We will take the help of an eclipse debugger to understand the flow of execution. I will encourage everyone to start debugging the web app as it will help us to have a batter clarity.
----------
Here is the video map :
Video contains : 00:00:00
Why Late upload? : 00:02:16
Adding a communication channel to our app: 00:06:20
Do's and Don't: 00:12:56
How to handle nested objects: 00:15:01
Why a Formatter is required: 00:24:58
Formartter introduction : 00:37:00
Printer and Parser deep dive: 00:38:51
Writing a Phon number formatter: 00:40:00
Registering the formatter with the app: 00:44:00
Print method Logic implementation: 00:53:53
Parse method implementation : 01:06:49
Bug Fixes: 01:24:11
Assignment one (Defect) : 01:35:55
Assignment two (Story): 01:40:28
Wait for a Twist: 01:45:23
Bye Bye: 01:52:00
