How eramis152/proyecto-sepa works
Project type and purpose
• Proyecto-SEPA is a full-stack web application whose sole business function is to convert transaction data acquired from an external web page into a SEPA-compliant XML file.
• The backend is a Spring Boot microservice (Java 17+) exposing a REST endpoint; the frontend is an Angular single-page application (SPA) that calls that endpoint.
File structure
• Top-level directories:
• src/main/java/com/sepa/back_end – contains the Spring Boot application class, REST controllers, CORS config, entity models, and XML generator utilities.
• src/main/java/com/sepa/front_end – contains the Angular project (package.json, tsconfig.json, src/app/components, services, routing, styles).
• xml – target folder where the generated XML is written.
• target – Maven build output (back_end.jar) and compiled frontend assets packaged inside the JAR.
• doc/documentation – JavaDoc and PDF user manual.
• Configuration files: pom.xml (Maven), angular.json, package.json, shell/batch scripts to install dependencies and start each service.
Main components
a. User Web Browser (Angular SPA)
b. Frontend App Server (Node runtime hosting Angular dev server) – optional in dev
c. REST API Backend (Spring Boot Application)
d. XML Generator Module (XmlGenerator utility)
e. File Store (xml/info.xml folder)
f. External Validation Service (third-party SEPA validator)
Relationships and data flows
1. User interacts with the Angular SPA in the browser (HTTP(S) requests).
2. SPA calls the Spring Boot REST endpoint (/transactions) via HTTP, subject to CORS (WebConfig).
3. TransactionController processes the request, maps to Transaction entity, and delegates to XmlGenerator.
4. XmlGenerator writes the SEPA XML file into the local xml/ directory.
5. User downloads or retrieves the XML from the backend (or directly from the xml/ folder).
6. User submits the XML to the external validation service.
Architectural patterns and technologies
• SPA + REST API separation
• MVC on the backend: Controller (TransactionController), Model (Transaction entity), Utility (XmlGenerator)
• CORS configuration for cross-origin calls
• Build tools: Maven (backend), npm/Node (frontend)
• Packaging: the Angular build is bundled into the Spring Boot JAR under resources/static for production.
4. Inside the API rectangle, subdivide into:
• Controllers (TransactionController)
• Entities (Transaction)
• Utils (XmlGenerator)
• CORS Config (WebConfig)