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

Bug 326798

Summary:	Configure Virgo's processing of Web Application Bundle manifest headers to conform strictly to the OSGi web spec by default
Product:	[RT] Virgo	Reporter:	Glyn Normington <glyn.normington>
Component:	unknown	Assignee:	Project Inbox <virgo-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	2.1.0.M04-incubation
Target Milestone:	3.0.0.M06
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Glyn Normington

2010-10-01 12:14:00 EDT

As described in bug 326754, Virgo 2.1.x deliberately modifies the behaviour of Gemini Web so that it is not strictly compliant with the OSGi spec but *is* compatible with dm Server 2.0.x.

In a later version of Virgo, we should switch this behaviour so that Virgo is strictly compliant. This will force certain applications to change, so we should consider an appropriate backwards compatibility header, or other configuration, to use in such cases.

Comment 1 Glyn Normington

2010-10-04 07:18:59 EDT

I have documented the current behaviour in the "Known Issues" section of the Programmer Guide and noted that we may change to match the OSGi spec post 2.1.x.

Comment 2 Glyn Normington

2011-06-07 06:28:36 EDT

As documented in the User Guide, there is a new configuration file:

config/org.eclipse.virgo.web

which has a property:

WABHeaders=strict|defaulted

strict is the default. defaulted is the 2.x behaviour and issues a message (WE0006W) warning that the option may not be supported in future releases.