I would never use PTC's recommendation on this as documented. It performs with issues sometimes. Here is the output from my codebase/netmarkets/util/begin_custom.jspf
YOU DO NOT NEED TO RESTART. Clearing browser cache and it shows immediately on a hot live system.
Seen no performance problems due to this...
<%@ page import="java.io.BufferedReader,java.io.File,java.io.FileReader,java.io.IOException,wt.util.WTProperties" %>
<%
// THIS CODE HANDLES DISPLAYING MESSAGE TO END USERS
// WHILE THE SYSTEM IS RUNNING - I.E. TO PROVIDE WARNING OF UNEXPECTED SHUTDOWN
// OR TO DISPLAY A BASELINE OF CONFIGURATIONS UNDER GOING DEVELOPMENT AND TESTING
// DO NOT MAKE CHANGES TO THIS CODE AS THIS AFFECTS SYSTEM CONFIGURATION MANAGEMENT
// PLEASE CHANGE THE TEXT CONTENT OF THE BANNER.TXT FILE TO CHANGE THE MESSAGE.
//
// THE PTC CUSTOMIZERS GUIDE USES DIFFERENT CODE THAT REQUIRES TOMCAT TO BE RESTARTED
// WHICH IS A POOR DESIGN.
//
// TO HAVE NO BANNER MESSAGE APPEAR, ELIMINATE OR COMMENT OUT
// THE TEXT BETWEEN THE <DIV>THIS TEXT</DIV>
// ELEMENT IN BANNER.TXT
//
// Contact: david.demay@trw.com 04/08/2010
//
BufferedReader input = null;
try
{
WTProperties trw_wt_properties_obj_instance = WTProperties.getLocalProperties();
String codebasePath = trw_wt_properties_obj_instance.getProperty("wt.codebase.location");
input = new BufferedReader(new FileReader(new File(codebasePath + "/netmarkets/jsp/util/banner.txt")));
String line = null;
while (( line = input.readLine()) != null)
{
out.println(line); // print file being read in at runtime to client output on browser, etc.
}
out.flush();
}
catch (IOException error) {
// do nothing to print error message in client window - you'll just not see banner
error.printStackTrace(System.err); // to tomcat log
}
finally {
input.close();
}
%>
<%-- PLACE ADDITIONAL JSP, JAVA, HTML, OR JAVASCRIPT CODE DOWN HERE AS NEEDED --%>
