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

Bug 325917

Summary: Server integration with Tomcat 7.0.2 doesn't allow Tomcat to display any web pages
Product: [WebTools] WTP ServerTools Reporter: Dean Schulze <dean_w_schulze>
Component: jst.serverAssignee: Larry Isaacs <larryisaacs>
Status: RESOLVED INVALID QA Contact: Angel Vera <arvera>
Severity: major    
Priority: P3 CC: jarthana, larryisaacs
Version: 3.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Dean Schulze CLA 2010-09-21 22:18:55 EDT 
Build Identifier: 20100617-1415

I have a web application with Tomcat 7.0.2 as the server.  When I start Tomcat with Eclipse and go to http://localhost:8080/ it shows
    The requested resource (/) is not available.

There's nothing in the logs.

If I shut down Tomcat from within Eclipse and start it with startup.bat it displays the normal Tomcat home page.

Reproducible: Always

Steps to Reproduce:
1.  Create a web application
2.  Add Tomcat 7 as server
3.  Start through Eclipse
Comment 1 Jay Arthanareeswaran CLA 2010-09-22 03:35:37 EDT 
Moving to Web tools.
Comment 2 Larry Isaacs CLA 2010-09-22 08:55:55 EDT 
This is expected behavior.  Please see the Tomcat FAQ (http://wiki.eclipse.org/WTP_Tomcat_FAQ) for the reasons why and other details about the WTP Tomcat support, specifically:

http://wiki.eclipse.org/WTP_Tomcat_FAQ#If_I_start_my_Tomcat_server_and_try_to_display_Tomcat.27s_default_page.2C_why_do_I_see_a_directory_listing_or_404_error_page.3F

Note: If you are trying to deploy your project as the "ROOT" web application, go to the Web Project Settings in the Project properties and set the "Context root" to "/".  Setting it to and empty string would also work except that an empty setting isn't currently accepted.  When the Tomcat server is published, the "Path" attribute for the <Context> associated with the project will be adjusted to be just "" rather than "/", making it the default context.  Avoiding "auto-deployment" is what makes this possible, and may be one of the reasons the WTP Tomcat support doesn't work quite as you expect.  Again, see the Tomcat FAQ for details.

Resolving as INVALID since this is expected behavior, i.e. creating a new Tomcat server defaults to creating a new separate Tomcat server instance, which doesn't include the default Tomcat webapps.