[writetosuman]

Hi,

I’m using MyEclipse4.1GA on Eclipse 3.1.2. I configured Tomcat5.5.12 inside MyEclipse to start from inside ME. I have the deploy/redeploy feature in ME on other normal Web project which works fine. But when I tried to redeploy the Tapestry project the deployment fails. Even the older deployment becomes unavailable.

The console shows:
Feb 12, 2006 5:03:45 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive TestProject.war
Feb 12, 2006 5:04:27 PM org.apache.catalina.startup.HostConfig checkResources
INFO: Undeploying context [/TestProject]
Feb 12, 2006 5:04:28 PM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive TestProject.war
Feb 12, 2006 5:04:29 PM org.apache.catalina.startup.ContextConfig applicationWebConfig
INFO: Missing application web.xml, using defaults only StandardEngine[Catalina].StandardHost[localhost].StandardContext[/TestProject]

Thank you,
Suman

[Riyad Kalla]

Suman

1) It looks like you named your Tapestry project the same as your other project. So when you say “Even the older deployment becomes unavailable” it’s because you are overwriting it.

2) The error says you are missing a web.xml file. Is this Tapestry project a Web Project? If so, open up the properties and got MyEclipse-Web, what 2 values do you have for the text boxes there?

3) Don’t deploy to a running application server. What can happen is the app server can attempt to deploy the web application from the WAR before MyEclipse is done creating the WAR file, which will cause it to die because it’s an invalid ZIP file.

[Disgruntled]

I was getting this same error message. It seems that MyEclipse was having trouble re-deploying to Tomcat because one of the JAR files deployed to the server was in use. In my case, it was ehcache-1.1.jar that was in use. I poked around in some forums and found some advice that suggested creating the file /META-INF/context.xml with the following in it:

<Context reloadable=”true” antiJARLocking=”true” antiResourceLocking=”true”>
</Context>

These context attributes prevent Tomcat from locking JAR files etc. I have not had the missing web.xml error message since making this change. **** You should consider turning off these flags when deploying to a production server as they result in a performance impact. See this page from the Tomcat documentation for more information:

http://tomcat.apache.org/tomcat-5.5-doc/config/context.html

[Riyad Kalla]

This is a very helpful followup, thank you Disgruntled.

[Author]

Posts