Migrate JBoss Web Valves to JBoss EAP 7 Undertow Handlers

From JBoss EAP 7.1 Migration Guide:

"5.14. Migrate Custom Application Valves

You must manually migrate custom valves or any valves that are defined in the jboss-web.xml XML file. This includes valves created by extending the org.apache.catalina.valves.ValveBase class and configured in the <valve> element of the jboss-web.xml descriptor file.

IMPORTANT
Custom valves and valves that are defined in the jboss-web.xml file must be rewritten or replaced by the corresponding Undertow built-in handler. For information about mapping valves to Undertow handlers, see Migrate JBoss Web Valves.

Authentication valves must be replaced manually using Undertow built-in authentication mechanisms.

Migrate Valves Configured in Deployments

In JBoss EAP 6, you could define custom valves at the application level by configuring them in the jboss-web.xml web application descriptor file. In JBoss EAP 7, it is possible to do this with Undertow handlers as well.

The following is an example of a valve configured in the jboss-web.xml file in JBoss EAP 6.

<jboss-web>
<valve>
<class-name>org.jboss.examples.MyValve</class-name>
​ <param>
​ <param-name>myParam</param-name>
​ <param-value>foobar</param-value>
​ </param>
</valve>
</jboss-web>

For more information about how to create and configure custom handlers in JBoss EAP, see Creating Custom Handlers in the JBoss EAP Development Guide.

Migrate Custom Authenticator Valves

For information about how to migrate authenticator valves, see Security Application Changes."

RHAMT already includes a rule wrt JBoss Web Valves, developed by WINDUPRULE-59, which now should be updated, since these Valves may now be replaced by Undertow Handlers. It's not possible to automate such migration though, perhaps the user should just be alerted of the need to migrate to Undertow Handlers, and be redirected to JBoss EAP 7.1 Migration Guide for always up to date manual migration guidance.