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

Bug 322265

Summary:	Web-ContextPath doesn't seem to have any effect unless deployed as part of a PAR.
Product:	[RT] Virgo	Reporter:	Tim Goeke <tim.goeke>
Component:	unknown	Assignee:	Glyn Normington <glyn.normington>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	minor
Priority:	P3	CC:	glyn.normington, zteve.powell
Version:	unspecified
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Tim Goeke

2010-08-10 14:11:23 EDT

Build Identifier: Virgo M2

The Web-ContextPath header seems to have no effect when deploying a standalone web module.

Reproducible: Always

Steps to Reproduce:
1. Deploy the greenpages solution PAR.
2. The web application is at the context /greenpages
3. Deploy just the WAR, greenpages.web.  (You may need to deploy the deps manually or comment out the service reference.)
4. The web application deploys at the context /greenpages.web

Comment 1 Steve Powell

2010-08-19 06:19:41 EDT

Thank you for raising this problem.

Are you deploying from STS or by dropping in pickup or using Admin Console?

A blow-by-blow account of the 'deploy the deps' would be helpful, too.  Thanks.

Comment 2 Glyn Normington

2010-09-03 11:16:50 EDT

I tried to reproduce this bug with a known good web module from the Gemini Web project (org.eclipse.gemini.web.test/src/test/resources/specified-context-path-1.war).

The web module has the following manifest:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.1
Implementation-Title: war-with-servlet
Bundle-ClassPath: WEB-INF/classes,WEB-INF/lib/[...]
Implementation-Version: 1.0.0.BUILD-20090423071040
Created-By: 1.6.0_07-b06-57 (Apple Inc.)
Bundle-ManifestVersion: 2
Import-Package: javax.servlet;version="2.5.0",javax.servlet.http;versi
 on="2.5.0",javax.servlet.jsp;version="2.1.0",javax.servlet.jsp.el;ver
 sion="2.1.0",javax.servlet.jsp.tagext;version="2.1.0",javax.el;versio
 n="1.0.0"
Web-ContextPath: /specified
Bundle-SymbolicName: specified-context-path-1

This is deemed to be a web module according to the OSGi Web Applications Spec because the Web-ContextPath is specified (as "/specified" just for added confusion ;-) ).

Deploying this into pickup in Virgo web server milestone 4 yields the following messages:

[2010-09-03 16:07:53.674] fs-watcher                   <HD0001I> Hot deployer processing 'CREATED' event for file 'specified-context-path-1.war'. 
[2010-09-03 16:07:53.714] fs-watcher                   <DE0000I> Installing bundle 'specified-context-path-1' version '0.0.0'. 
[2010-09-03 16:07:53.847] fs-watcher                   <DE0001I> Installed bundle 'specified-context-path-1' version '0.0.0'. 
[2010-09-03 16:07:53.915] fs-watcher                   <DE0004I> Starting bundle 'specified-context-path-1' version '0.0.0'. 
[2010-09-03 16:07:53.920] Thread-3                     <WE0000I> Starting web bundle 'specified-context-path-1' version '0.0.0' with context path '/specified'. 
[2010-09-03 16:07:54.069] Thread-3                     <WE0001I> Started web bundle 'specified-context-path-1' version '0.0.0' with context path '/specified'. 
[2010-09-03 16:07:54.072] start-signalling-4           <DE0005I> Started bundle 'specified-context-path-1' version '0.0.0'.

Perhaps the web module you were deploying had a Web-ContextPath specifying /greenpages.web?

Please could you attach the exact web application you are using so we can try to reproduce what you are seeing.