Liferay hooks won't work when deployed when the portal deployment descriptor has a display-name property

• Type: Regression Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.X, 7.1.X
• Fix Version/s: 7.0.0 DXP FP89, 7.0.10.13 DXP SP13, 7.0.X, 7.1.10 DXP FP15, 7.1.X, 7.2.10 DXP FP2, 7.2.10.1 DXP SP1, 7.2.X, Master
• Component/s: Portal Services > Component Management > Hot Deployment
• Labels:
  • ee-ts
  • liferay-dxp-70-sp13
  • liferay-dxp-72-sp1
  • liferay-fixpack-de-89-7010
  • liferay-fixpack-dxp-15-7110
  • liferay-fixpack-dxp-2-7210
• Branch Version/s:
  7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/79085

Steps to reproduce

1. Deploy Liferay DXP 7.0 (fix pack de-30 or more recent) on Websphere following the documented instructions;
   1. or, alternatively, if you prefer to reproduce this on Tomcat, you need to use a non-empty value for <display-name> on web.xml. Websphere adds a display-name when deploying Liferay
2. Deploy the attached hook liferay-hook.war .

Expected result

The sample filter will be deployed and the init method of the custom filter will print a stack trace on the logs. Also, subsequent requests will also print a stack trace in the logs from the method doFilter of the custom filter.

Actual result

The sample filter war will be deployed but the custom filter won't be added to the filter list.

Additional notes

This is caused by LPS-74219.