##Basic
This application was built as part of the coursework for Enterprise Application Development course at San Jose State University. A set of REST APIs are built to manage entities and relationships in a mini gaming website.
##Usage
There are two primary types of entities: Players and Sponsors. They have the following relationships and constraints:
- Opponents: if two players play against each other, they are opponents. The opponent relationship is symmetric in that is Alice is an opponent of Bob, then Bob is also an opponent of Alice. A player can have zero or more opponent players.
- Sponsors: a player can optionally be sponsored by an external sponsor. Different players can have the same sponsor.
- The firstname, lastname, and email fields are required for any player. Emails have to be unique across players.
- The name field is required for any Sponsor, and does not need to be unique.
##Features The application supports the following APIs:
- Create a player
- Get a player
- Update a player
- Delete a player
- Create a Sponsor
- Get a Sponsor
- Update a Sponsor
- Delete a Sponsor
- Add an opponent
- Delete an opponent
##Implementation details :
- Spring boot is used to build and run the REST APIs and Chrome plugin POSTMAN for testing the API URLs and viewing the json outputs.
- Local instance of MYSQL database and Hibernate ORM Mapping using XMLs is used to store the persistent data.
##Tools
- Eclipse with Spring Boot plug-in
- mysql Workbench to execute queries
- Postman REST Client for testing the REST APIs