How codeforge-dosw/techcup-futbol-backend-springboot works
TechCup Fútbol is a Spring Boot REST backend for managing football tournaments, teams, players and users, protected by JWT authentication. The main workflow is a client request entering a controller, passing through a domain service for validation and operations, and reaching repositories for persistence; mappers translate between persistence entities and API/domain models. The README also describes match, lineup, invitation and related football-domain capabilities, but their runtime implementation is not shown in the excerpts. Edges reflect the README or SOURCE INDEX references; unsampled behavior is not inferred.
Main entry points: TeamService.java Team service · UserService.java User service · TournamentService.java Tournament service · UserMapper.java User mapper
Components 24
REST API
- Authentication API
src/main/java/edu/eci/dosw/tech_cup/controller/AuthController.java - Team API
src/main/java/edu/eci/dosw/tech_cup/controller/TeamController.java - Tournament API
src/main/java/edu/eci/dosw/tech_cup/controller/TournamentController.java - User API
src/main/java/edu/eci/dosw/tech_cup/controller/UserController.java - API documentation
src/main/java/edu/eci/dosw/tech_cup/config/SwaggerConfig.java
Identity and access
- Security configuration
src/main/java/edu/eci/dosw/tech_cup/security/SecurityConfig.java - JWT request filter
src/main/java/edu/eci/dosw/tech_cup/security/JwtAuthenticationFilter.java - JWT service
src/main/java/edu/eci/dosw/tech_cup/service/JwtService.java
Tournament operations
- User service
src/main/java/edu/eci/dosw/tech_cup/service/UserService.java - Team service
src/main/java/edu/eci/dosw/tech_cup/service/TeamService.java - Tournament service
src/main/java/edu/eci/dosw/tech_cup/service/TournamentService.java
Football domain and persistence
- User repository
src/main/java/edu/eci/dosw/tech_cup/repository/UserRepository.java - Team repository
src/main/java/edu/eci/dosw/tech_cup/repository/TeamRepository.java - Team-player repository
src/main/java/edu/eci/dosw/tech_cup/repository/TeamPlayerRepository.java - Tournament repository
src/main/java/edu/eci/dosw/tech_cup/repository/TournamentRepository.java - User mapper
src/main/java/edu/eci/dosw/tech_cup/mapper/UserMapper.java - Team mapper
src/main/java/edu/eci/dosw/tech_cup/mapper/TeamMapper.java - Tournament mapper
src/main/java/edu/eci/dosw/tech_cup/mapper/TournamentMapper.java - User and role records
src/main/java/edu/eci/dosw/tech_cup/entity/UserEntity.java - Team records
src/main/java/edu/eci/dosw/tech_cup/entity/TeamEntity.java - Team-player records
src/main/java/edu/eci/dosw/tech_cup/entity/TeamPlayerEntity.java - Tournament records
src/main/java/edu/eci/dosw/tech_cup/entity/TournamentEntity.java - Football domain models
src/main/java/edu/eci/dosw/tech_cup/model
Other components
- API client
Connections 29
- API client → Authentication API: submits login
README.md - API client → Team API: calls endpoints
README.md - API client → Tournament API: calls endpoints
README.md - API client → User API: calls endpoints
README.md - Authentication API → JWT service: uses tokens
src/main/java/edu/eci/dosw/tech_cup/controller/AuthController.java - Security configuration → JWT request filter: configures filter
src/main/java/edu/eci/dosw/tech_cup/security/SecurityConfig.java - JWT request filter → JWT service: validates tokens
src/main/java/edu/eci/dosw/tech_cup/security/JwtAuthenticationFilter.java - Team API → Team service: delegates to
src/main/java/edu/eci/dosw/tech_cup/controller/TeamController.java - Tournament API → Tournament service: delegates to
src/main/java/edu/eci/dosw/tech_cup/controller/TournamentController.java - User API → User service: delegates to
src/main/java/edu/eci/dosw/tech_cup/controller/UserController.java - User service → User repository: reads and writes
src/main/java/edu/eci/dosw/tech_cup/service/UserService.java - User service → User mapper: maps users
src/main/java/edu/eci/dosw/tech_cup/service/UserService.java - Team service → Team repository: reads and writes
src/main/java/edu/eci/dosw/tech_cup/service/TeamService.java - Team service → Team-player repository: records roster
src/main/java/edu/eci/dosw/tech_cup/service/TeamService.java - Team service → Tournament repository: checks tournament
src/main/java/edu/eci/dosw/tech_cup/service/TeamService.java - Team service → User repository: checks captain
src/main/java/edu/eci/dosw/tech_cup/service/TeamService.java - Team service → Team mapper: maps teams
src/main/java/edu/eci/dosw/tech_cup/service/TeamService.java - Tournament service → Tournament repository: reads and writes
src/main/java/edu/eci/dosw/tech_cup/service/TournamentService.java - Tournament service → Tournament mapper: maps tournaments
src/main/java/edu/eci/dosw/tech_cup/service/TournamentService.java - User repository → User and role records: persists
src/main/java/edu/eci/dosw/tech_cup/repository/UserRepository.java - Team repository → Team records: persists
src/main/java/edu/eci/dosw/tech_cup/repository/TeamRepository.java - Team-player repository → Team-player records: persists
src/main/java/edu/eci/dosw/tech_cup/repository/TeamPlayerRepository.java - Tournament repository → Tournament records: persists
src/main/java/edu/eci/dosw/tech_cup/repository/TournamentRepository.java - User mapper → User and role records: maps from
src/main/java/edu/eci/dosw/tech_cup/mapper/UserMapper.java - User mapper → Football domain models: maps to
src/main/java/edu/eci/dosw/tech_cup/mapper/UserMapper.java - Team mapper → Team records: maps from
src/main/java/edu/eci/dosw/tech_cup/mapper/TeamMapper.java - Team mapper → Football domain models: maps to
src/main/java/edu/eci/dosw/tech_cup/mapper/TeamMapper.java - Tournament mapper → Tournament records: maps from
src/main/java/edu/eci/dosw/tech_cup/mapper/TournamentMapper.java - Tournament mapper → Football domain models: maps to
src/main/java/edu/eci/dosw/tech_cup/mapper/TournamentMapper.java