Project

General

Profile

Actions

Anomalie #45

open

Resolve the JAR conflict between Liferay and JasperReports Server

Added by François Cerbelle over 10 years ago. Updated about 10 years ago.

Status:
Nouveau
Priority:
Normal
Target version:
Start date:
11/11/2013
Due date:
% Done:

0%

Estimated time:

Description

The Liferay portal application and all the Liferay portlets applications need a portal-service.jar to be in the classpath. As soon as this JAR is deployed, either in the Tomcat's global classpath (<TOMCATDIR>/lib) or in the liferay portal app private classpath (webapps/lportal/WEB-INF/lib) or in the portlet applications private classpath (webapps/*/WEB-INF/lib), JasperReports Server is unable to display reports in JIVE. It loops on the spinning icon when asking for a report to be executed. When directly executing a report from Adhoc to an export format, it works. So, I guess that the conflict impacts only JIVE.


Related issues 1 (1 open0 closed)

Blocks Evolution #29: Installing Liferay 6 and the PortletEn coursFrançois Cerbelle10/31/2013

Actions
Actions #1

Updated by François Cerbelle over 10 years ago

  • Subject changed from Resolve the JAR conflict to Resolve the JAR conflict between Liferay and JasperReports Server
Actions #2

Updated by François Cerbelle over 10 years ago

  • Target version changed from 5.5.0-1 to 5.5.0-2
Actions #3

Updated by François Cerbelle over 10 years ago

Currently, the only answer I had was that using one tomcat instance to serve more than one webapp is a "bad practice". Which would mean 6 tomcat instances in the VM and does not solve the issue.

Actions #4

Updated by François Cerbelle about 10 years ago

  • Target version changed from 5.5.0-2 to 5
Actions #5

Updated by François Cerbelle about 10 years ago

  • Target version changed from 5 to Later
Actions

Also available in: Atom PDF