-
-
Notifications
You must be signed in to change notification settings - Fork 364
IHandlerActivator
IHandlerActivator
is the handler activator, and it should be able to instantiate handlers.
When a message comes in and needs to be handled, Rebus will pass the message down through the pipeline for incoming messages.
Unless you have changed the default behavior, the message will at some point reach the ActivateHandlersStep
which will use the IHandlerActivator
and call GetHandlers<TMessage>()
on it, expecting in return a sequence of objects that implements IHandleMessages<TMessage>
.
The resulting handler instances will be stored in the incoming step context, allowing the DispatchIncomingMessageStep
to dispatch the message to them.
Basic stuff
- Home
- Introduction
- Getting started
- Different bus modes
- How does rebus compare to other .net service buses?
- 3rd party extensions
- Rebus versions
Configuration
Scenarios
Areas
- Logging
- Routing
- Serialization
- Pub sub messaging
- Process managers
- Message context
- Data bus
- Correlation ids
- Container adapters
- Automatic retries and error handling
- Message dispatch
- Thread safety and instance policies
- Timeouts
- Timeout manager
- Transactions
- Delivery guarantees
- Idempotence
- Unit of work
- Workers and parallelism
- Wire level format of messages
- Handler pipeline
- Polymorphic message dispatch
- Persistence ignorance
- Saga parallelism
- Transport message forwarding
- Testing
- Outbox
- Startup/shutdown
Transports (not a full list)
Customization
- Extensibility
- Auto flowing user context extensibility example
- Back off strategy
- Message compression and encryption
- Fail fast on certain exception types
Pipelines
- Log message pipelines
- Incoming messages pipeline
- Incoming step context
- Outgoing messages pipeline
- Outgoing step context
Prominent application services