[David]

I have an Web project I am trying to run with Tomcat 5. I use myEclipse to deploy and start Tomcat. I am unable to connect to my Servlet defined in the Tomcat\webapps\OfficialCheck\WEB-INF\web.xml and looking at the console I see this:

INFO: Missing application web.xml, using defaults only StandardEngine[Catalina].StandardHost[localhost].StandardContext[/OfficialCheck]

Here is how I have my server.xml under Tomcat5\conf\
<Context path=”/OfficialCheck” reloadable=”true”
docBase=”C:\eclipse\workspace\OfficialCheck”
workDir=”C:\eclipse\workspace\OfficialCheck\work” />

I do not know why Tomcat cannot pickup the web.xml when it can clearly see the directory. I prove this by hitting : http://localhost/OfficialCheck/login.html

Any ideas, this is really starting to get irritating.

[Scott Anderson]

Rather than trying to configure Tomcat to point to your workspace, you’ll likely find it much easier to use an unmodified Tomcat server and let our deployer deploy to it automatically. An example using Tomcat in this way is in the Working with Web Projects tutorial in the Documentation section here.

[David]

How does this impact me when I want to move to code to production? I will not be able to use myEclipse to create the WAR file and have it start tomcat for me, correct? Or am I mistaken in thinking that I have to modify the server.xml in Tomcat to pickup the appliction I place under the webapps directory?

[kalpitan]

This problem happens under the circumstance that the web application reads or writes to files on the physical disk (in the exploded web app) and does not close the file.

In such a case, when the webapp is redeployed it attempts to delete the previous deployment but is unable to because the files in question are in use (from the previous deployment). Hence the partial deletion of the old deployment leaves the webapp incomplete and misses the web.xml file.

The solution to the problem is that ensure that in the code you are closing any disk files accessed in the webapp folder.

[Author]

Posts