What problem does it solve?
Ecotone developers often face inconsistent patterns when creating message handlers. This skill provides a unified approach to declare and wire CommandHandler, EventHandler, QueryHandler, and ServiceActivator with correct endpointIds, routing, and metadata.
Core Features & Use Cases
- Class-based routing: Use type-hinted message classes to route to handlers automatically.
- Routing-key flexibility: Annotate with a string-based routing key for integration scenarios.
- Endpoint configuration: Enforce unique endpointId per handler and ensure proper output channels.
- Header metadata access: Use #[Header] to read message headers in handlers.
- Documentation & examples: See API references and usage examples for ready-to-copy patterns.
Quick Start
Create a sample OrderService with CommandHandler, EventHandler, and QueryHandler annotated methods to demonstrate routing and endpointId usage.