docs: 统一中间件定位与 JDBC 轮询主路径口径

Align README, architecture, design, config comments, and ingress docs
with the upstream message-processing middleware model: external CIIMS write
to CMINMSGS, JDBC poll as production ingress, HTTP /cminmsgs/send as compat.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
windyboy
2026-09-07 10:27:44 +08:00
co-authored by Cursor
parent 8c8d2613c2
commit 7ccdd00a31
13 changed files with 198 additions and 94 deletions
@@ -2,6 +2,11 @@
## 0. 文档说明
> **nextgen 定位注(msgexchange-v2**:本文件描述 **legacy** 行为基线。nextgen 为**上游报文
> 处理中间件**——生产主路径 = JDBC 轮询共享 MySQL `CMINMSGS`(上游经 CIIMS 等外部落信);
> legacy §3.1 HTTP 收报与 §3.2 轮询在现役并存,nextgen 将轮询提升为主拓扑、HTTP 降为 compat
> (见仓库 `docs/architecture.md`)。
- 本文档记录 msgexchange-api(现役旧项目)的完整业务逻辑,并以用户故事形式组织,作为新系统(Micronaut + Kotlin)迁移设计及一致性对拍的行为基线。
- 内容依据仓库源码与资源配置编写:`src/main/java/com/gzzn/omms/msgexchange-api/**``src/main/resources/*.yml`;分支 `feature/add_dev_containers_supports`HEAD `eb72a668`)。
- 报文结构依据 `SIS_AODB_RMS-V0.1.md``unisysaodbsis.xsd`(同目录 docs/legacy/)。