How flyingimmortal/jarpress works
Project type and purpose
• This is a backend-focused, full‑stack system (Jarpress) built on Spring Boot + MyBatis.
• Its goal is to expose WordPress content via a unified API, support H5/Uni‑app/Mini‑program/WeChat clients, and integrate with WordPress without plugins or schema changes.
File structure
• Top‑level Maven multi‑module:
• seifly‑common: shared utilities, annotations, AOP aspects, filters, Redis caching, cross‑cutting framework code.
• seifly‑javapress: core domain definitions (DDD entities, enums, constants).
• javapress‑dao: persistence layer using MyBatis mappers to WordPress tables.
• javapress‑business: domain services implementing business rules and use‑cases (CommentsService, PostsService, etc.).
• javapress‑app: Spring Boot application layer (controllers, interceptors, REST/OpenAPI config, security, JWT, WxConfig).
• External artifacts: WordPress MySQL database (doc/db scripts), Redis (caching), external WeChat APIs.
Key README insights
• Core tech: Java 8, Spring Boot 2.7.x, MyBatis, SpringDoc OpenAPI.
• DDD layering: application layer (controllers) → business/core domain services → persistence.
• Frontends live in separate repo (Uni‑app + Vant Weapp for Mini‑program).