This is an odd scenario, but I've repeated it several times, just to make sure.

I'm using Tomcat 4.0.4b2.  I have a simple Struts application, which I got
mostly working with Struts 1.1b2.

In my Ant "deploy" target, before copying the WAR, I use a command-line
interface to the Manager app to "stop" the application, then I copy the WAR,
and then use the same command-line app to "start" the application.

This was working fine when my Struts application was using the binary release
of Struts 1.1b2.

I then installed all the latest CVS code for Struts and Commons and built it
all.  In my application source tree, I have a "weblib" directory that I store
the jars my application is using.  I renamed the existing directory that had
the jars from Struts 1.1b2, and created a new one, then copied in all the newly
built Struts & Commons jars, and then I rebuilt and redeployed the application.

At this point, my application is seeing one problem with finding message
resources, which I'm still trying to figure out, and which I'm asking about on
the Struts list.

However, I'm seeing another symptom that seems to only involve Tomcat, but it
only occurs when I switch to building with the latest Struts/Commons.  It
doesn't occur when the application is built with the binary Struts 1.1b2
release.

The issue is that when I rerun the application after restarting it through the
Manager, I get the following exception (truncated):

javax.servlet.jsp.JspException: Exception forwarding for name main: 
java.lang.ClassCastException: org.apache.struts.action.RequestProcessor
        at org.apache.struts.taglib.logic.ForwardTag.doEndTag(ForwardTag.java:180)
        at org.apache.jsp.index$jsp._jspService(index$jsp.java:77)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)

This doesn't happen if I restart Tomcat (I just get the messages problem).

-- 
===================================================================
David M. Karr          ; Java/J2EE/XML/Unix/C++
[EMAIL PROTECTED]


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to