pariharashish/dgh

Purpose and runtime

This is a Maven-based Java/Spring backend for managing oil-and-gas domain data: basins, contract areas, facilities, wells, tanks, devices, operators, tariffs, users, access control, alerts, change requests, audits, and reports. The application entry point is src/main/java/com/logicladder/dgh/DghApplication.java; environment-specific Spring properties are under src/main/resources/application.properties and src/main/resources/application-*.properties.

HTTP API boundary

REST controllers are the inbound boundary, organized by domain and reporting:

• src/main/java/com/logicladder/dgh/controller/WellController.java

• src/main/java/com/logicladder/dgh/controller/DeviceController.java

• src/main/java/com/logicladder/dgh/controller/reports/GlobalReportsController.java

Requests pass through request/response logging and centralized exception handling at src/main/java/com/logicladder/dgh/components/RequestResponseLoggingInterceptor.java and src/main/java/com/logicladder/dgh/configuration/GlobalExceptionHandler.java. DTOs form the API contract boundary before persistence/domain mapping, e.g. src/main/java/com/logicladder/dgh/dto/WellDto.java.

Authentication and authorization

JWT authentication is exposed through src/main/java/com/logicladder/dgh/security/controller/AuthenticationRestController.java. Token extraction, validation, and Spring Security integration are centered on:

• src/main/java/com/logicladder/dgh/security/JwtAuthorizationTokenFilter.java

• src/main/java/com/logicladder/dgh/security/JwtTokenUtil.java

• src/main/java/com/logicladder/dgh/security/config/WebSecurityConfig.java

Authorization appears to be role/page-group based, persisted through src/main/java/com/logicladder/dgh/entity/app/AccessRolePageGroup.java and accessed through src/main/java/com/logicladder/dgh/security/repository/IAccessRolePageGroupRepository.java.

Core business and persistence layers

Controllers delegate to interface-driven services and implementations, which operate on JPA entities and repositories/DAOs. Representative flow is controller → service → repository/DAO → relational persistence:

• src/main/java/com/logicladder/dgh/service/impl/WellServiceImpl.java

• src/main/java/com/logicladder/dgh/security/repository/IWellRepository.java

• src/main/java/com/logicladder/dgh/entity/app/Well.java

The repository contains both Spring Data-style repositories and custom generic DAO implementations, with transaction setup in src/main/java/com/logicladder/dgh/configuration/JpaTransactionConfig.java. Dozer mappings support DTO/entity conversion via src/main/java/com/logicladder/dgh/configuration/DozerConfig.java.

Logic Ladder integration and asynchronous workflows

A distinct integration layer synchronizes or orchestrates domain actions with an external “Logic Ladder” service. It has domain-specific interfaces/implementations for wells, devices, facilities, contract areas, alerts, and change requests:

• src/main/java/com/logicladder/dgh/logic/ladder/service/impl/WellLogicLadderServiceImpl.java

• src/main/java/com/logicladder/dgh/logic/ladder/service/impl/DeviceLogicLadderServiceImpl.java

• src/main/java/com/logicladder/dgh/logic/ladder/service/impl/AsyncLogicLadderServiceImpl.java

External request/response schemas are isolated under src/main/java/com/logicladder/dgh/thirdparty/request/dto/ and src/main/java/com/logicladder/dgh/thirdparty/response/dto/. RestTemplate configuration at src/main/java/com/logicladder/dgh/configuration/RestTemplateConfig.java is the likely outbound HTTP client boundary.

Audit, notifications, and reporting

Hibernate insert/update listeners provide a cross-cutting audit/event capture path:

• src/main/java/com/logicladder/dgh/hibernate/events/HibernateInsertUpdateEventListener.java

• src/main/java/com/logicladder/dgh/entity/app/AuditLog.java

• src/main/java/com/logicladder/dgh/entity/app/EventLog.java

User/operator lifecycle actions generate templated email notifications through src/main/java/com/logicladder/dgh/service/impl/MailServiceImpl.java and FreeMarker templates in src/main/resources/templates/. SMS capability is represented by src/main/java/com/logicladder/dgh/util/CallSmscApi.java.

Reporting includes API-configurable boards/endpoints and Jasper report generation:

• src/main/java/com/logicladder/dgh/controller/reports/config/BoardConfigServiceImpl.java

• src/main/java/com/logicladder/dgh/controller/reports/jasper/AbstractReportGenerator.java

• src/main/resources/templates/DGHReportTemplate.jrxml