shanmukha5269/collabhub

Purpose and Runtime

CollabHub is a Java/Spring Boot backend for collaborative workspaces combining member management, project planning (projects, sprints, issues), channels/messages, and administrator controls. The application entry point is backend/collabHub/src/main/java/com/collabHub/CollabHubApplication.java; Maven build/runtime dependencies are defined in backend/collabHub/pom.xml.

API and Layering Boundary

Each domain follows controller → service interface/implementation → JPA repository → entity, with DTOs separating HTTP/WebSocket contracts from persistence models. Representative boundaries are backend/collabHub/src/main/java/com/collabHub/workspace/controller/WorkspaceController.java, backend/collabHub/src/main/java/com/collabHub/workspace/service/WorkspaceServiceImpl.java, and backend/collabHub/src/main/java/com/collabHub/workspace/repository/WorkspaceRepository.java.

Identity, Authentication, and Authorization

Users have roles and status, while authentication exposes login-related APIs and issues/validates JWTs. Requests traverse the JWT filter and Spring security configuration before protected controllers; services can obtain the authenticated identity through shared security utilities. Core paths: backend/collabHub/src/main/java/com/collabHub/auth/security/JwtAuthenticationFilter.java, backend/collabHub/src/main/java/com/collabHub/auth/security/JwtTokenProvider.java, backend/collabHub/src/main/java/com/collabHub/config/SecurityConfig.java.

Workspace as the Tenancy/Membership Root

A workspace is the primary collaboration boundary, with a separate membership association and workspace-scoped roles. Workspace APIs cover creation, member changes, and ownership transfer; suspended-workspace handling is represented as a domain exception and administrator operation. Core paths: backend/collabHub/src/main/java/com/collabHub/workspace/entity/Workspace.java, backend/collabHub/src/main/java/com/collabHub/workspace/entity/WorkspaceMember.java, backend/collabHub/src/main/java/com/collabHub/workspace/service/WorkspaceMemberServiceImpl.java.

Planning Domain

Projects, sprints, and issues form the work-management flow. Projects provide the planning container; sprints have lifecycle status and expose board-oriented responses; issues carry type, priority, and status and support status-specific updates. These services enforce domain lookup/access before repository persistence. Core paths: backend/collabHub/src/main/java/com/collabHub/project/service/ProjectServiceImpl.java, backend/collabHub/src/main/java/com/collabHub/sprint/service/SprintServiceImpl.java, backend/collabHub/src/main/java/com/collabHub/issue/service/IssueServiceImpl.java.

Collaboration and Realtime Messaging

Channels and channel membership model conversation access. Messages are persisted via the message service/repository and exposed by a message controller. STOMP WebSocket configuration and a connection listener provide the realtime transport boundary, alongside the HTTP APIs. Core paths: backend/collabHub/src/main/java/com/collabHub/config/StompWebSocketConfig.java, backend/collabHub/src/main/java/com/collabHub/listener/WebSocketConnectListener.java, backend/collabHub/src/main/java/com/collabHub/message/service/MessageServiceImpl.java.

Administration, Persistence, and Failure Semantics

Administrative APIs aggregate platform/workspace statistics and suspend workspaces. Persistence is Spring Data-style repository-backed, with concrete database and runtime settings expected in backend/collabHub/src/main/resources/application.properties and environment inputs documented by backend/collabHub/.env.example. Domain failures are normalized at the HTTP boundary through backend/collabHub/src/main/java/com/collabHub/common/exception/GlobalExceptionHandler.java; specific exceptions encode access denial, bans, missing resources, and suspended workspaces.