tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Appling" <sajaka...@mindspring.com>
Subject Problem resolving TagExtraInfo class right after startup
Date Thu, 18 Nov 2004 21:33:45 GMT
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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message