When released, you should be able to take a war file to any container (JSP2.0) and it should work solid. We do not make a war file, as the class files and config files keep changeing.
With Tomcat, sometimes you have to manualy delete the cache directory (under \work) but with Resin 3.0 you do not have to do that. Each container has it's little quirks, these are 2 of the best.
(JBoss ships in 4.0 with Tomcat).
And it is possible that you added a bug.
.V
Doug Shackelford wrote:
I'm trying to understand the interaction between platform (Linux, Win2000/XP, etc.), app servers (TomCat, Resin, etc.), and different Java implementations (Sun, Bea, IBM, etc.).
Assume that you are redeploying a WAR file many times by copying it to the distribution folder of the app server. Everything is cool for a while, but then you get errors. The WAR file is consistent, but it won't deploy. You can reboot and everything will be fine. In some cases, you can restart the app server, and everything will be fine. My question is who should I blame first? Maybe I should blame myself...if so, tell me why.
When I used JBoss/Jetty/Sun on Linux, I never had this problem. Now, I'm using Tomcat/Sun on Win2000 and I have the problem. I have some suspicions, but I don't want to influence the audience.
And if my question is totally off the wall, then send me a private e-mail.
--Doug
-- Vic Cekvenich, Struts Instructor, 1-800-917-JAVA
Advanced <a href ="baseBeans.com">Struts Training</a> and project recovery in North East. Open Source <a href ="baseBeans.com">Content Management</a> basicPortal sofware Best practice<a href ="baseBeans.com">Struts Support</a> v.1.1 helper ScafflodingXPress
_______________________________________________ MVC-Programmers mailing list [EMAIL PROTECTED] http://www.basebeans.net:8080/mailman/listinfo/mvc-programmers
