what makes a Tomcat5.5 cannot be "aware" of new Java Web Applications?
- by Michael Mao
This is for uni homework, but I reckon it is more a generic problem to the Tomcat Server(version 5.5.27) on my uni.
The problem is, I first did a skeleton Java Web Application (Just a simple Servlet and a welcome-file, nothing complicated, no lib included) using NetBeans 6.8 with the bundled Tomcat 6.0.20 (localhost:8084/WSD)
Then, to test and prove it is "portable" and "auto-deploy-able", I cleaned and built a WSD.war file and dropped it onto my Xampp Tomcat (localhost:8080/WSD). The war extracted everything accordingly and I can see identical output from this Tomcat. So far, so good.
However, after I tried to drop to war onto uni server, funny thing happens:
uni server
Even though I've changed the war permission to 755, it is simply not "responding".
I then copied the extracted files to uni server, the MainServlet cannot be recognized from within its Context Path "/WSD", basically nothing works, expect the static index.jsp. I tried several times to stop and restart uni Tomcat, it doesn't help?
I wonder what makes this happen? Is there anything I did wrong with my approach?
To be frank I paid no attention to a server not under my control, and I am unfortunately not a real active day-to-day Java Programmer now. I understand the fundamentals of MVC, Servelets, JSPs, JavaBeans, but I really feel frustrated by this, as I cannot see why...
Or, should I ask, a Java Web Application, after cleaned and built by NetBeans6.8, is self-contained and self-configured so ready to be deployed to any Java Web Container?
I know, I can certainly program everything in plain old JSP, but this is soooo... unacceptable to myself...
Update :
I am now wondering if there is any free Tomcat Hosting so that I would like to see if my war file and/or my web app can go with them without any configuration at all?
