Jboss/Tomcat using wrong classloader on redeploy

[digitalwarrior]

Hello,

We recently moved to JBoss 3.0.6 w/ Tomcat 4.1.18 integrated but I'm having one difficulty setting it up in our development environment.

In production, we use an ear file without any problem, but in development, we like to put jar files in the deploy directory and then have a Context set to direct any jsps or servlets to a fixed directory (eg "E:\resellers\webroot"). This makes it easier to edit/recompile/view individual jsps and makes for much faster development.

The problem is with the new JBoss I am at a loss for figuring out how to do this. The element in tomcat41-service.xml doesn't support path and/or docBase attributes. Normally it would be done in the server.xml file in tomcat-4.1.x/conf, but that file is no longer used in the new JBoss, correct?

Anyone have any ideas how I would go about doing this?

Thank you,

Ram

[digitalwarrior]

I solved my own problem after 2 months of looking.
Struts is the issue.

I could not get this error to occur when using straight Servlets, so it made me put my focus on struts. i'm currently using Struts 1.0.2.

I downloaded the RC1 of Struts 1.1 and ran my same code using it and this problem did not happen. Hot deploy is now working.

JBoss and/or Tomcat were not the issue.