Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 323594

Summary: Unable to launch web project in Tomcat 6.0
Product: [WebTools] WTP ServerTools Reporter: Jaap <jaap>
Component: jst.serverAssignee: Larry Isaacs <larryisaacs>
Status: RESOLVED WORKSFORME QA Contact: Angel Vera <arvera>
Severity: major    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard:

Description Jaap CLA 2010-08-25 07:50:39 EDT
Build Identifier: 20100617-1415

I'm trying to deploy the shindig web project to a tomcat 6.0 server in eclipse.

When I start tomcat 6.0 in eclipse servers view, it gives the following error:
SEVERE: Error starting static Resources
java.lang.IllegalArgumentException: Document base C:\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\shindig-server does not exist or is not a readable directory.

Checking the directory I see that wtpwebapps only has a ROOT folder.

I tried the publish option but nothing shows up.

I see two configuration directories and I'm confused as to which is used.

I looks like that the configuration is pointing to a path which is not being created.

Reproducible: Always

Steps to Reproduce:
1. Download eclipse J2EE Helios
2. install maven plugins
3. checkout shinding from trunk
4. import existing maven project
5. Add tomcat 6.0 server
6. configure module shindig-server

Result:

Server.xml in tmp0/conf directory has a Context referencing to a non-existing directory. It is the directory
Comment 1 Larry Isaacs CLA 2011-02-10 12:29:23 EST
If you create a new Dynamic Web Project and try to publish it instead of shindig, does it have the same problem?  The steps don't mention it, but to make sure, confirm that the "Serve modules without publishing" option is not enabled in the server editor.  Also, check the Error Log view to see if there is anything there related to publishing the server.

At this moment, it's possible that steps 2 through 4 (primarily 4) are the source of this behavior.  The last time I messed with maven (which was years ago) it was to investigate a different "odd behavior" type bug in Eclipse.  It was confirmed that maven was misconfiguring the Dynamic Web Project and causing the undesired behavior.
Comment 2 Larry Isaacs CLA 2011-04-07 13:18:21 EDT
Marking as WORKSFORME until additional information is available.  There isn't enough information to determine why "wtpwebapps/shindig-server" was not created.  It could be something related to maven, since I don't have maven installed to confirm if it has issues.  We can re-open when there is more information to work with.