This repository demonstrates a WeChat public account (official account) backend implementation using Spring MVC and the WeChat Java SDK. It handles incoming messages from WeChat servers, verifies request authenticity, routes messages to appropriate handlers based on type, and generates responses. The application follows a layered architecture with controllers for HTTP endpoints, a service layer that encapsulates WeChat SDK interactions, and specialized handlers for different message types (text, location, menu events, subscribe/unsubscribe, etc.). The message handling mechanism uses a router pattern where different message types are directed to specific handler implementations. Each handler extends an abstract base class that provides common utilities like JSON parsing and logging. The builder pattern is employed for constructing response messages, with separate builders for different message types (text, image, etc.). The application also includes endpoints for managing custom menus via the WeChat API. While the codebase shows good separation of concerns and proper use of design patterns, some handlers contain TODO comments indicating areas for further implementation. The demo nature of the project means it focuses on illustrating core concepts rather than providing a fully-featured production application. Configuration is externalized via Spring XML and Java config, with WeChat credentials stored in properties files.
WeRoBot is a Python library for building WeChat Official Account (ε ¬δΌε·) robots. It provides a high-level framework that handles message parsing, event routing, signature verification, session management (with multiple backends like SQLite, Redis, MongoDB), message encryption/decryption (AES), and a full client for the WeChat Corporate API (menu management, user management, template messages, mass messaging, etc.). The library can run as a standalone WSGI application (via Bottle) or be integrated into Django, Flask, Bottle, and Tornado. The core robot class (WeRoBot) allows developers to register handlers via decorators for specific message types (text, image, location) and events (subscribe, click, scan). It is a mature, well-documented project with comprehensive test coverage and CI/CD. The codebase is generally well-structured but shows signs of technical drift in dependency versions and Python version support (officially tested up to Python 3.9, some pinned libraries are outdated).