ariludev/serviciosweb

1. System purpose and runtime shape

Restaurantito is a JHipster 9.1-generated full-stack application: an Angular single-page application (SPA) is served alongside a Java/Spring Boot backend. The implemented business surface is currently identity, account lifecycle, user administration, authority management, and operational administration; no restaurant-domain entities appear in the tree.

Backend entry points are src/main/java/com/edosushi/RestaurantitoApp.java (executable Spring Boot app) and src/main/java/com/edosushi/ApplicationWebXml.java (WAR deployment). Frontend boots from src/main/webapp/main.ts through src/main/webapp/bootstrap.ts.

2. Angular SPA composition

Angular routing and dependency configuration form the client composition root:

• src/main/webapp/app/app.config.ts

• src/main/webapp/app/app.routes.ts

• src/main/webapp/app/app.ts

The SPA is structured around account flows, login, home/layout, admin operational pages, and generated user/authority management pages. Feature routes render within the main layout. Spanish UI translations are present under src/main/webapp/i18n/es/; backend messages also support default and Spanish bundles.

3. Client authentication and HTTP boundary

The client authentication layer holds account state, acquires JWTs, and protects routes:

• src/main/webapp/app/core/auth/account.service.ts

• src/main/webapp/app/core/auth/auth-jwt.service.ts

• src/main/webapp/app/core/auth/user-route-access.service.ts

Global HTTP interceptors attach auth, react to expiry, normalize errors, and issue notifications:

• src/main/webapp/app/core/interceptor/auth.interceptor.ts

• src/main/webapp/app/core/interceptor/auth-expired.interceptor.ts

• src/main/webapp/app/core/interceptor/error-handler.interceptor.ts

Primary client flow: route guard → feature service HTTP call → interceptor adds JWT → Spring REST endpoint → response updates UI/account state. The backend’s SPA filter handles browser-side route fallback.

4. REST, account, and administration layer

Spring MVC resources expose the API boundary for authentication, self-service account operations, public users, authorities, and administrator user management:

• src/main/java/com/edosushi/web/rest/AuthenticateController.java

• src/main/java/com/edosushi/web/rest/AccountResource.java

• src/main/java/com/edosushi/web/rest/UserResource.java

Request view models isolate login/managed-user payloads, while centralized exception translation maps failures to HTTP problem responses:

• src/main/java/com/edosushi/web/rest/vm/LoginVM.java

• src/main/java/com/edosushi/web/rest/errors/ExceptionTranslator.java

• src/main/java/com/edosushi/web/filter/SpaWebFilter.java

5. Security and user-domain core

Security is Spring Security with JWT configuration, domain-backed user lookup, authorities, and audit identity:

• src/main/java/com/edosushi/config/SecurityConfiguration.java

• src/main/java/com/edosushi/config/SecurityJwtConfiguration.java

• src/main/java/com/edosushi/security/DomainUserDetailsService.java

The core persisted model is User plus Authority, with a shared audit base. UserService implements registration, activation, password reset/change, and admin user operations; mail delivery supports lifecycle emails:

• src/main/java/com/edosushi/domain/User.java

• src/main/java/com/edosushi/service/UserService.java

• src/main/java/com/edosushi/service/MailService.java

6. Persistence, configuration, and lifecycle

Spring Data repositories persist users and roles. Database schema and seed users/authorities are managed through Liquibase:

• src/main/java/com/edosushi/repository/UserRepository.java

• src/main/resources/config/liquibase/master.xml

• src/main/resources/config/liquibase/changelog/00000000000000_initial_schema.xml

Profile-specific application behavior resides in:

• src/main/resources/config/application.yml

• src/main/resources/config/application-dev.yml

• src/main/resources/config/application-prod.yml

Configuration covers database connectivity, caching, async execution, JSON/Hibernate behavior, logging, static resources, TLS, and security. Mail templates are a backend-to-email-provider boundary under src/main/resources/templates/mail/.

7. Build, deployment, and observability

Maven packages the Java service and integrates the Angular build; Angular CLI/esbuild builds the browser bundle. Production can be executable JAR or WAR (pom.xml, angular.json).

Docker Compose provides PostgreSQL and complete app/service orchestration:

• src/main/docker/postgresql.yml

• src/main/docker/services.yml

• src/main/docker/app.yml

Operational monitoring is provisioned with Prometheus and Grafana, while JHipster Control Center and SonarQube are optional external services:

• src/main/docker/monitoring.yml

• src/main/docker/prometheus/prometheus.yml

• src/main/docker/jhipster-control-center.yml