aayushsirsat02/sample-generator

Purpose and entry point

This is a Maven-packaged Java report-management application. The runtime entry point is src/main/java/com/sample_generator/sample/SampleApplication.java; the built executable is target/sample-0.0.1-SNAPSHOT.jar. It serves a login/dashboard UI and controller-driven operations for sample reports, assets, users, companies, and market segments.

Web and presentation boundary

HTTP requests enter controller classes under src/main/java/com/sample_generator/sample/controller/, notably SampleReportController.java, AssetController.java, and LoginController.java. Server-rendered pages reside in src/main/resources/templates/dashboard.html and src/main/resources/templates/login.html; browser behavior and styling are delivered from src/main/resources/static/js/dashboard.js and src/main/resources/static/css/dashboard.css.

Report workflow

SampleReportController.java accepts report-facing requests and delegates business operations to SampleReportService.java / SampleReportServiceImpl.java. Request and response boundaries are explicit in DTOs such as CreateSampleReportRequest.java, SampleReportDetailResponse.java, and SampleReportListResponse.java. Report configuration/reference concerns are separated into ReportConfigService.java and AssetReferenceService.java.

Domain and persistence

The core domain is modeled through JPA-style entities: SampleReport.java, Asset.java, Company.java, MarketSegment.java, User.java, and Role.java. Repository interfaces form the persistence boundary, including SampleReportRepository.java, AssetRepository.java, and UserRepository.java. A local MVStore database artifact is present at data/sample_report_db.mv.db, indicating file-backed H2-compatible development/runtime storage.

Authentication and administration

Security policy is centralized in src/main/java/com/sample_generator/sample/config/SecurityConfig.java. User lookup for authentication is handled by src/main/java/com/sample_generator/sample/security/CustomUserDetailsService.java; login routing/UI is in LoginController.java and the login templates. Administrative user operations are exposed separately through AdminUserController.java, preserving a distinct admin control boundary.

Initialization and failure handling

src/main/java/com/sample_generator/sample/config/DataInitializer.java seeds or prepares application data at startup. src/main/java/com/sample_generator/sample/controller/GlobalExceptionHandler.java provides a cross-controller error boundary so service, validation, and persistence failures can be converted into consistent HTTP responses.

Runtime and deployment artifacts

The project uses Maven wrapper launch/build infrastructure (mvnw, .mvn/wrapper/maven-wrapper.properties) and application configuration in src/main/resources/application.properties. Windows-oriented execution scripts (run_jar.cmd, run_mvnw.cmd) support launching either the packaged JAR or Maven runtime. External-service evidence is limited; the repository primarily contains a self-contained web application with local database state and static assets.