yasithdev opened a new pull request, #595: URL: https://github.com/apache/airavata/pull/595
## Summary - Create new `airavata-thrift-server` Maven module isolating all thrift server concerns - Move thrift IDL files (`thrift-interface-descriptions/` → `airavata-thrift-server/src/main/thrift/`) - Move server bootstrap (`AiravataServer`), main handler (`AiravataServerHandler`, `ThriftAdapter`), profile handlers, and `OrchestratorServerHandler` to the new module - Add 33 proto3 definitions mirroring all thrift IDL data models in `airavata-api/src/main/proto/` - Configure protoc compilation in `airavata-api` and MapStruct in `airavata-thrift-server` - Add representative `WorkspaceMapper` demonstrating proto↔thrift mapping pattern ## Architecture ``` airavata-thrift-server (NEW) ├── depends on: airavata-api ├── owns: thrift IDL, server bootstrap, thrift handlers, MapStruct mappers └── src/main/thrift/ (moved from thrift-interface-descriptions/) airavata-api (SLIMMED) ├── owns: service layer, data access handlers, background services ├── owns: proto definitions + protoc generation └── src/main/proto/ (NEW — 33 files) ``` Data-access handlers (`RegistryServerHandler`, `SharingRegistryServerHandler`, `CredentialStoreServerHandler`) remain in `airavata-api` since the service layer depends on them directly. Full thrift removal from `airavata-api` is planned as follow-up work. ## Test plan - [x] `mvn clean compile -T4` — BUILD SUCCESS across all 8 modules - [x] No stale handler references in `airavata-api` - [x] Proto compilation generates Java classes from all 33 `.proto` files - [x] MapStruct annotation processing configured and compiling - [ ] Integration tests (require Docker/Derby infrastructure) ## Spec & Plan - Design spec: `docs/superpowers/specs/2026-03-26-airavata-thrift-server-extraction-design.md` - Implementation plan: `docs/superpowers/plans/2026-03-26-airavata-thrift-server-extraction.md` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
