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

Bug 387368

Summary:

The J2EE preview Server can not serve any pages.

Product:

[WebTools] WTP ServerTools

Reporter:

Kirby Zhou <kirbyzhou>

Component:

wst.server

Assignee:

wst.server <wst.server-inbox>

Status:

RESOLVED DUPLICATE

QA Contact:

Elson Yuen <eyuen7>

Severity:

major

Priority:

CC:

thatnitind

Version:

3.4

Target Milestone:

---

Hardware:

All

OS:

All

Whiteboard:

Attachments:

Description	Flags
screenshot	none

Description Kirby Zhou

2012-08-16 06:24:15 EDT

0. Download eclipse-jee version Juno and unpack it.
1. New a Dynamic Web Project
2. Choose 'J2EE Preview' as its Server.
3. New a jsp or a html page
4. Run it on Server.
5. The 404 response appears.

Error 404 - Not Found

No context on this server matched or handled this request.
Contexts known to this server are:
TestWeb(/TestWeb)



-- Configuration Details --

org.eclipse.wst.server.preview.adapter_1.1.100.v20120517_1638
org.eclipse.wst.server.preview_1.1.101.v20111212_1019
org.eclipse.jdt 3.8.0.v20120525-1249-8-8nFqlFNOfwKDRGz-pXLdGxEM83

Product: 
Eclipse 1.5.0.20120131-1544 (org.eclipse.epp.package.jee.product)

Comment 1 Nitin Dahyabhai

2012-08-23 11:47:22 EDT

Created attachment 220204 [details]
screenshot

Attaching a screenshot showing this exact problem with eclipse-jee-juno-win32.zip and:
java version "1.7.0_01"
Java(TM) SE Runtime Environment (build 1.7.0_01-b08)
Java HotSpot(TM) Client VM (build 21.1-b02, mixed mode)

This is the generated preview.xml found in my d:\wtp34\workspace.clean\.metadata\.plugins\org.eclipse.wst.server.core\tmp0 directory (workspace location is d:\wtp34\workspace.clean on 64-bit Windows 7):

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<server port="8080">
  <module context="d" name="d" path="D:/wtp34/workspace.clean/.metadata/.plugins
/org.eclipse.wst.server.core/tmp0/d" type="j2ee"/>
</server>

Comment 2 Elson Yuen

2012-08-23 12:45:18 EDT

This problem is caused by bug 366092

*** This bug has been marked as a duplicate of bug 366092 ***