The Dispatch Pipeline
2 min read
2 min read
2 min read
2 min read
2 min read
2 min read
An object adapter dispatches each incoming request through its dispatch pipeline, a chain of dispatchers.
The request first goes through the middleware of the object adapter, in installation order. A middleware usually passes the request to the next dispatcher, but can also return a response itself, such as an error.
Once the request has gone through all the middleware, the object adapter dispatches the request to a servant. It looks for this servant in the following order:
- The servant in its active servant map (ASM) for the identity and facet of the request.
- The default servant registered for the category of the identity.
- The default servant registered for the empty category.
- A servant provided by a servant locator. Don't use servant locators in new applications.
When the object adapter finds no servant, the dispatch fails with FacetNotExistException if the ASM has a servant for the identity of the request with another facet, and with ObjectNotExistException otherwise.