On Thursday, October 31, 2002, at 04:32 AM, busch@xxxxxxxxxxxxxxxx
wrote:
You shouldn't have to do anything special. Did you restart tomcat
after
moving the jar files? You shouldn't have to change your app's
Server.ClassPath[] (unless it has relative path names in it).
Of course I restarted Tomcat
Putting the libs into the webapps directory results in an
ClassCastException for some reason...
When is this exception being thrown?
When I try to first access a page from Enhydra-Context. The
Stacktrace starts with a Ajp13 Class in the beginning, and on the
top it said ClassCastException for the class which extends the
Enhydra StandardApplication class
Danny
Its hard to see exactly what's going on here. In the first case (with
AutoReload = true), the enhydra HttpPresentationServlet is calling
application.getClass().getClassLoader() and casting the result to
MultiClassLoader...but the result is actually a
org.apache.catalina.loader.StandardClassLoader object, so its throwing
an exception.
In the second case (AutoReload = false), it looks like the "state"
instance variable of StandardApplication is being set to
Application.INCOMPLETE at some point, so when your app gets a request,
HttpPresentationServlet first calls your app's "restartup" method, and
the default implementation of this (in StandardApplication) does
nothing but throw the ApplicationException you see. However it doesn't
look like enhydra will ever set the application's state to
INCOMPLETE...is it possible you do this somewhere in your application?
Are you setting "<load-on-startup>1</load-on-startup>" in the app's
web.xml file? Does the application seem to start up properly (display
enhydra startup message, etc.)? Did you try adding DEBUG to the app
conf's Server.LogToFile[] line to see if anything unusual showed up?
Scott
| 