Deploying a Portlet to Liferay 6.2 on Tomcat 8, causes listerner tags in Web.xml of portlet to change to Context-param tags

Issue

• 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&gt;com.xyz.SpringContextLoaderListener</listener-class&gt; </listener> <listener> <listener-class&gt;com.xyz.CustomStartupListener</listener-class&gt; </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>

Environment

• Portal 6.2

Resolution

• 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.