- Deploying a portlet developed for Liferay 6.2 on Tomcat 7, on a Liferay 6.2 instance running on Tomcat 8 causes the portlet's web.xml file to reflect the following changes:
The web.xml before it is deployed had the following listener tags
<listener> <listener-class>com.xyz.SpringContextLoaderListener</listener-class> </listener> <listener> <listener-class>com.xyz.CustomStartupListener</listener-class> </listener>
- The listener tags are condensed into a single context-param tag shown below, after it is deployed:
<context-param> <param-name>portalListenerClasses</param-name> <param-value>com.xyz.SpringContextLoaderListener,com.xyz.CustomStartupListener</param-value> </context-param>
- Portal 6.2
- This is caused by https://issues.liferay.com/browse/LPS-26321 and is an expected behavior.
- As a workaround, editing the web.xml file of the portlet and restoring the listener tags to the prior syntax resolves the issue.
Subscriber Exclusive Content
A Liferay Enterprise Subscription provides access to over 1,500 articles that include best practices, troubleshooting, and other valuable solutions. Sign in for full access.Sign In