Custom WildFly JBossWeb Valve: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
This article explains how to write and deploy a custom Tomcat valve into WildFly/EAP JBossWeb runtime. For details on how to write and deploy a custom Tomcat valve into a Tomcat container, see {{Internal|Custom Tomcat Valve|Custom Tomcat Valve}} | This article explains how to write and deploy a custom Tomcat valve into WildFly/EAP JBossWeb runtime. For details on how to write and deploy a custom Tomcat valve into a Tomcat container, see {{Internal|Custom Tomcat Valve|Custom Tomcat Valve}} | ||
A custom valve can be deployed globally as part of the JBossWeb [[Tomcat Concepts#Engine|Engine]]'s [[Tomcat_Concepts# | A custom valve can be deployed globally as part of the JBossWeb [[Tomcat Concepts#Engine|Engine]]'s [[Tomcat_Concepts#Request_Processing_Pipeline|request processing pipeline]], or embedded with an application, part of the [[Tomcat_Concepts#Context|Context]]'s request processing pipeline. | ||
Revision as of 23:21, 27 February 2017
Internal
Overview
This article explains how to write and deploy a custom Tomcat valve into WildFly/EAP JBossWeb runtime. For details on how to write and deploy a custom Tomcat valve into a Tomcat container, see
A custom valve can be deployed globally as part of the JBossWeb Engine's request processing pipeline, or embedded with an application, part of the Context's request processing pipeline.