When WABHeaders = strict we don't. As the manifest you are providing only contains the 'Manifest-Version' header i suspect it is getting transformed in to Bundle-ManifestVersion = 2 as it is assuming it is a version 1 manifest. The extra headers are getting added when that happens. I don't know how it is getting picked up as a web bundle though with out the Web-ContextPath header?
Chris.
From: "Violeta Georgieva" <milesg78@xxxxxxxxx>
To: "Virgo Project" <virgo-dev@xxxxxxxxxxx>
Sent: Thursday, 11 August, 2011 4:54:47 PM
Subject: [virgo-dev] Plain Web Applications are not transformed on Virgo 3.0.0.RC2?
Hi,
Since 3.0.0.M06 we do not add the defaults: Bundle-ManifestVersion; Bundle-SymbolicName; Bundle-ClassPath; Import-Package; to Web Application Bundle Manifest.
But I thought that we still add this to Plain Web Application Manifest.
Unfortunately this is not the behaviour of 3.0.0.RC2.
In my Web Application Manifest I have:
Manifest-Version: 1.0
1) When WABHeaders=strict
I have this:
osgi> h 117
Bundle headers:
Bundle-ManifestVersion = 2
Bundle-SymbolicName = context.xml.web-0.0.1
Manifest-Version = 1.0
Module-Type = web-bundle
Web-ContextPath = context.xml.web-0.0.1
2) When WABHeaders=defaulted
I have this:
osgi> h 107
Bundle headers:
Bundle-ClassPath = WEB-INF/classes,WEB-INF/lib/jtds-1.2.5.jar,WEB-INF/lib/tomca
t-dbcp.jar
Bundle-ManifestVersion = 2
Bundle-SymbolicName = context.xml.web-0.0.1
Import-Package = javax.crypto.interfaces;version="[0.0.0, 0.0.0]",org.omg.CosNa
ming.NamingContextPackage;version="[0.0.0, 0.0.0]",org.omg.DynamicAny.DynAnyFact
oryPackage;version="[0.0.0, 0.0.0]",org.eclipse.osgi.internal.provisional.verifi
...
Manifest-Version = 1.0
Module-Type = web-bundle
Web-ContextPath = context.xml.web-0.0.1
org-eclipse-gemini-web-DefaultWABHeaders = true
osgi>
Do I miss something or we have a bug here?
Regards
Violeta
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
