explain why miidleware may not be called

Author: zamronypj

Diff for: dispatcher/index.md

@@ -106,10 +106,10 @@ container.add(
     )
 );
 ```
-## Set dispatcher
+## <a name="set-dispatcher"></a> Set dispatcher
 
-Fano Framework allows application to change dispatcher implementation to use by
-overriding `buildDispatcher()` method of `TBasicServiceProvider` class. In this method implementation, you must returns
+Fano Framework allows application to change dispatcher implementation to use, by
+overriding protected `buildDispatcher()` method of `TBasicServiceProvider` class. In this method implementation, you must returns
 instance of dispatcher.
 
 ```
@@ -119,6 +119,40 @@ begin
 end;
 ```
 
+If you use Fano CLI to [scaffold your web application project](/scaffolding-with-fano-cli), you can declared `buildDispatcher()` in `bootstrap.pas` file as shown in following example.
+
+```
+TAppServiceProvider = class(TDaemonAppServiceProvider)
+protected
+    function buildDispatcher(
+        const ctnr : IDependencyContainer;
+        const routeMatcher : IRouteMatcher;
+        const config : IAppConfiguration
+    ) : IDispatcher; override;
+    ...
+end;
+...
+function TAppServiceProvider.buildDispatcher(
+    const ctnr : IDependencyContainer;
+    const routeMatcher : IRouteMatcher;
+    const config : IAppConfiguration
+) : IDispatcher;
+begin
+    ctnr.add('appMiddlewares', TMiddlewareListFactory.create());
+
+    ctnr.add(
+        'my-dispatcher',
+        TDispatcherFactory.create(
+            ctnr['appMiddlewares'] as IMiddlewareLinkList,
+            routeMatcher,
+            TRequestResponseFactory.create()
+        )
+    );
+    result := ctnr['my-dispatcher'] as IDispatcher;
+end;
+```
+See [example of adding dispatcher with middleware support](https://github.com/fanoframework/fano-csrf/blob/master/src/bootstrap.pas).
+
 ## Explore more
 
 - [Working with Router](/working-with-router)

Diff for: middlewares/index.md

@@ -362,6 +362,12 @@ var helloCtrlMiddleware : IMiddleware;
 helloCtrlMiddleware := TRequestHandlerAsMiddleware.create(helloController);
 ```
 
+## Middleware issues
+
+### Middleware is not being called
+
+When you attach middleware to a route but middleware is not being called, make sure you use [dispatcher implementation which supports middleware](/dispatcher#set-dispatcher). Middleware support is not enabled by default.
+
 ## Performance consideration
 
 Using middleware adds overhead as request must go multiple execution points before reaching actual request handler. Also, you need to aware that each middleware will call next middleware recursively so you should limit number of middlewares in use.