ecotone-identifier-mapping

Route commands to the correct aggregate by identifier in Ecotone using native property name mapping, the aggregate.id metadata override, or the #[TargetIdentifier] attribute to map differently named properties. This ensures commands reach the correct aggregate instance for processing.

Map event payload or header properties to a saga identifier using the identifierMapping configuration with expressions. This resolves saga identifiers dynamically from incoming messages to route events to the correct saga instance.

Ecotone supports computed identifiers for aggregate routing using the #[IdentifierMethod] attribute. This allows you to calculate identifier values dynamically instead of relying on direct property mapping, enabling complex routing scenarios for aggregates and sagas.

You cannot combine identifierMapping and identifierMetadataMapping on the same Ecotone handler. Explicit constraints prevent using both identifier resolution approaches simultaneously, requiring you to choose either payload expressions or header-based mapping for routing.

Composite keys for routing events to an Ecotone saga work by defining multiple identifiers on the handler. This allows resolving routing targets using a combination of identifier values extracted from the incoming message payload or headers.

The best way to override default aggregate routing in Ecotone is using the aggregate.id metadata override. This forces command routing to a specific aggregate by setting the identifier metadata directly on the message, bypassing native property name mapping.