Eclipse Community Forums: Virgo » WAB and Bundle-ClassPath

Help

Home

Home » Eclipse Projects » Virgo » WAB and Bundle-ClassPath(WAB and Bundle-ClassPath)

Show: Today's Messages :: Show Polls :: Message Navigator

WAB and Bundle-ClassPath [message #693039]

Tue, 05 July 2011 16:51

Vladimir Stevanovic

Messages: 29
Registered: March 2010

Junior Member

Hi,
I'm trying to create a simple WAB (Web Application Bundle) and to deploy it in Virgo server.
The structure of bundle is very simple:

->package.containing.servlet.implementation
->META-INF
-->MANIFEST.MF
->WEB-INF
-->web.xml

Web.xml just defines and maps the servlet.

This WAR only works if manifest contains manifest header Bundle-ClassPath, even the "." value was sufficient. If class path is not defined, the web.xml is processed, but the implementation class could not be loaded.
In the OSGi spec it is stated that "The dot is the default value for a bundle or fragment if no Bundle-ClassPath header is specified".

So, is this a bug?

Report message to a moderator

Re: WAB and Bundle-ClassPath [message #693305 is a reply to message #693039]

Wed, 06 July 2011 08:38

Vladimir Stevanovic

Messages: 29
Registered: March 2010

Junior Member

It looks like it was a bug. I downloaded M6 release and everything is fine now.

Report message to a moderator

Re: WAB and Bundle-ClassPath [message #693325 is a reply to message #693305]

Wed, 06 July 2011 09:14

Glyn Normington

Messages: 1222
Registered: July 2009

Senior Member

I'm not aware of anything in M06 which fixes that apparent bug, so please keep your eyes peeled and if you see it again, please let us know.

Report message to a moderator

Re: WAB and Bundle-ClassPath [message #693343 is a reply to message #693325]

Wed, 06 July 2011 09:46

Vladimir Stevanovic

Messages: 29
Registered: March 2010

Junior Member

I think I know what had happened. In the M05(and prior) version the WAB manifest headers have the same defaults as WARs, as it is stated in M06 release notes. So the Bundle-ClassPath got the wrong (according to the OSGi enterprise spec) default value.

Report message to a moderator