Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326798 - Configure Virgo's processing of Web Application Bundle manifest headers to conform strictly to the OSGi web spec by default
Summary: Configure Virgo's processing of Web Application Bundle manifest headers to co...
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: unknown (show other bugs)
Version: 2.1.0.M04-incubation   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: 3.0.0.M06   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-01 12:14 EDT by Glyn Normington CLA
Modified: 2011-07-01 07:18 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Normington CLA 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 CLA 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 CLA 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.