Apache Tomcat defect with version 7.0.50 will cause issues with Clarity

Discussion created by Nika_Hadzhikidi Employee on Mar 14, 2014
Latest reply on Mar 17, 2014 by Chris_Hackett

Apache Tomcat defect 56029 with version 7.0.50 is causing issues with Clarity on Filter portlet's creation

Apache Tomcat version 7.0.50 has a regression defect 56029:
56029 Ternary operator doesn't work as expected inside attributes in jspx pages

For more information please check the Apache page:

This defect causes the following issue with Clarity:

CLRT-73956 Create New Filter portlet does not create a new portlet. It navigates back to the list page of portlets.
Steps to Reproduce:
1. Login to clarity and navigate to Home->Portlets.
2. Click on New Portlet and select Filter portlet
Expected Result: We should get a new Create Filter portlet page as shown in screenshot filterPortlet.png  
Actual Result: We are not getting a new create filter portlet page and it is navigating back to the list page of portlets.  

Error message is thrown:
ERROR 2014-03-02 20:52:19,051 [http-bio-80-exec-299] vxml.VXMLService (clarity:yepse01:5074206__01E10F2C-792E-4D25-A336-1743C44B3B23:npt.filterPropertiesEntry) Exception in processing
com.niku.union.web.WebException: Portlet view processing failed for portlet: npt.filterProperties
at com.niku.union.web.XMLPageProcessor.processPage(
at com.niku.union.web.XMLPageProcessor.processPage(
Caused by: com.niku.union.web.WebException: Failed to process portlet npt.filterProperties
at com.niku.union.web.XMLPageProcessor.processPortletJSPX(
at com.niku.union.web.XMLPageProcessor.processPage(
... 35 more
Caused by: org.apache.jasper.JasperException: /WEB-INF/npt/jsp/portlets/filters/filterPortletProperties.jspx (line: 183, column: 75) "${active eq 1 and newPortlet ne 'true'}" contains invalid expression(s): javax.el.ELException: Failed to parse the expression [${activeeq1andnewPortletne'true'}]
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(

Please avoid using the following Apache Tomcat versions with Clarity: 7.0.50, 7.0.51. The defect is fixed in Apache Tomcat version 7.0.52.