After upgrading to 8.0.4, 9.1 (or later releases) custom pages are throwing system errors

Yellowfin FAQ shared this problem 11 months ago
Resolved

When upgrading to 8.0.4, or 9.1 (or any later releases) the upgrade runs successfully, however we now run into a JasperException error. This happens when trying to log in using a custom login JSP, or accessing any other custom JSP page.

d005220c944288914044252d7fca7cdc


cd29deb4e0dd142c75c7d2883eb554eb

Comments (1)

photo
1

In 8.0.4 and later releases, we've made changes relating to architecture modernization. Due to this some custom pages referencing older frameworks may no longer function correctly. To resolve these issues, please follow the steps below;


1. If you have a custom login page, you will need to do the following:


<%! TagUtil tagUtil = new TagUtil(); %>
<%
// If the login page cannot render, redirect for initialisation.
if (!tagUtil.isInitialisedForLogon(request, getServletContext())) {
%>
<jsp:forward page="logon.i4"/>
<%
return;
}
%>


2. If you have other custom JSP’s, you would have to do everything except the last step.

3. If you see the additional error message “No WebApplicationContext found: not in a DispatcherServlet request and no ContextLoaderListener registered?” in a custom JSP, add the following line after all imports:

<%@ include file="/includes/ContextCheck.jsp" %>


Note: This is also a rare occurrence where you may also need to create your own version of the contextcheck page and switching:


<html:text tabindex="1" property="email" onmousedown="emailOnClick(event);" styleClass="loginBox" />
to

<input type="text" tabindex="1" name="email" value="" onmousedown="emailOnClick(event);" />


If you are still having issues or unsure if this applies to you, please raise a ticket with our support team containing a detailed description of your issue (including screenshots), and include any relevant .jsps.


Regards,

The Yellowfin Support Team.

Comments have been locked on this page!