This page explains how a web-app should be configured in order to work properly with Makumba.
Makumba controller filter mapping#
In order to work properly, the following filter should be mapped in WEB-INF/web.xml:
<filter>
<filter-name>makumba_controller</filter-name>
<filter-class>org.makumba.controller.http.ControllerFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>makumba_controller</filter-name>
<url-pattern>*.jsp</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>makumba_controller</filter-name>
<url-pattern>*.jspx</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
</filter-mapping>
<filter-mapping>
<filter-name>makumba_controller</filter-name>
<url-pattern>/mak-tools</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>makumba_controller</filter-name>
<url-pattern>/mak-tools/*</url-pattern>
</filter-mapping>
- *.jsp: to enable authentication/authorisation on JSP page access, and to enable form processing
- *.jspx: to enable the source-code viewer for JSP files
- /mak-tools/ and /mak-tools/*: to enable the various Makumba tools, such as the MDD viewer.
Note
The /mak-tools path can be configured in Makumba.conf, see the Makumba tools path configuration
Note
In the first two filter mappings, the <dispatcher> elements are necessary because some servlet containers (e.g. Jetty 7) implement the <welcome-file-list> specification in such a way that an explicit setting is necessary for the filter to take effect on welcome pages.