We are occasionally having problems when compiling a JSP soon after Tomcat has started. It results in a compile time exception starting with " Failed to load or instantiate TagExtraInfo class: org.apache.taglibs.standard.tei.ForEachTEI"
I believe this is only happening when the JSP needs to be compiled, it includes custom actions using TagExtraInfo (like JSTL tags), and it is called soon after the server has started. The TagExtraInfo class is available and the page will compile fine if you visit it a second time, but I would like to avoid this situation. I believe this has been reported before on some mailing lists and in bugzilla - see (http://www.mail-archive.com/taglibs-user@jakarta.apache.org/msg07336.html, http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg56670.html, and http://issues.apache.org/bugzilla/show_bug.cgi?id=26270, and perhaps http://issues.apache.org/bugzilla/show_bug.cgi?id=27398. I'm willing to help look into this, but would like some pointers on where to start. Is it possible that all of the classloader framework is not initialized by the time Jasper starts to compile a page? Is there someone familiar with the startup process who might comment on whether this is a reasonable hypothesis or should I look elsewhere? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
