Is it just me, or is Catalina a lot more rigorous in its checks than previous tomcat versions?
I've got a webapp which works fine on the Jboss2.4.3/Tomcat3.2.3 bundle, but which throws all sorts of JSP complile time errors on the Jboss2.4.3/Catalina bundle.
For example at the top of one of my JSPs, I have the following:
<%@page errorPage="MainError.jsp" import="java.text.DateFormatSymbols,
java.text.DateFormat,
java.util.Date,
java.util.Calendar,
java.util.Collection,
java.util.Iterator,
javax.naming.InitialContext,
denny.wallpaper.Constants,
denny.wallpaper.log.LogFactory,
denny.wallpaper.ejb.Lesson,
denny.wallpaper.ejb.TeacherNugget,
denny.wallpaper.jsptools.LessonTools,
denny.wallpaper.jsptools.WallpaperSystemException,
org.apache.log4j.Category;"%>
<%!
DateFormatSymbols dfs = new DateFormatSymbols(Constants.getDateLocale());
String[] months = dfs.getMonths();
Calendar calendar = Calendar.getInstance(Constants.getDateLocale());
Category cat = LogFactory.getCategory("CreateLesson.jsp");
%>
Which generates a Class or interface expected message in Catalina, but not in 3.2.3
There are a few other things along similar lines.
Per-cue-li-are
Cheers
Peet
