Given five files,
PlayerController.javaPlayerRepository.javaPlayerH2Service.javaPlayerRowMapper.javaPlayer.java
And also given a database file cricketteam which contains TEAM table.
| Columns | Type |
|---|---|
| playerId | INTEGER |
| playerName | TEXT |
| jerseyNumber | INTEGER |
| role | TEXT |
Use only TEAM as a table name in your code while writing queries.
-
Player.java:Playerclass should contain the following attributes.Attribute Type playerId int playerName String jerseyNumber int role String -
PlayerRepository.java: Create aninterfacecontaining required methods. -
PlayerService.java: Update the service class with logic for managing player data. -
PlayerController.java: Create the controller class to handle HTTP requests. -
PlayerRowMapper.java: Create a class which implements theRowmapper Interface.
Implemented the following APIs.
Returns a list of all players in the team.
[
{
"playerId": 1,
"playerName": "Alexander",
"jerseyNumber": 5,
"role": "All-rounder"
},
...
]
Creates a new player in the team. The playerId is auto-incremented.
{
"playerName": "Prince",
"jerseyNumber": 24,
"role": "Bowler"
}
{
"playerId": 12,
"playerName": "Prince",
"jerseyNumber": 24,
"role": "Bowler"
}
Returns a player based on the playerId. If the given playerId is not found in the team, raise ResponseStatusException with HttpStatus.NOT_FOUND.
{
"playerId": 1,
"playerName": "Alexander",
"jerseyNumber": 5,
"role": "All-rounder"
}
Updates the details of a player in the team based on the playerId.
Also, return the updated player details from the TEAM using the playerId.
{
"playerName": "Yuvi"
"jerseyNumber": 12,
"role": "All-rounder"
}
{
"playerId": 3,
"playerName": "Yuvi",
"jerseyNumber": 12,
"role": "All-rounder"
}
Deletes a player from the team based on the playerId.
Do not modify the code in PlayerApplication.java