Community
Participate
Working Groups
This should be reproduced by deploying the Aries blog sample web bundle plus its immediate dependencies and seeing if the classes in the root of the bundle can be loaded by driving the web bundle through a browser. With version 0.2 of the web bundle, this resulted in a class loading failure and a workaround was to add: Bundle-ClassPath: . to the web bundle manifest. The same problem did not appear to recur with v0.3 of the web bundle, so care should be taken when reproducing this problem as the original symptoms may have been misinterpreted. I simply wanted to get this bug on the backlog so as not to forget to investigate it.
Setting priority to minor as no users have reported seeing this, users are unlikely to encounter it if they put their classes in WEB-INF/classes, and there is a trivial workaround if a user does hit it.
Virgo overrides the behaviour of Gemini Web so that it always defaults certain missing headers such as Bundle-ClassPath. This is a deliberate policy to provide compatibility between Virgo 2.1.x and dm Server 2.0.x. In a later version of Virgo, we can remove this behaviour to obtain strict OSGi spec behaviour for web applications.
See bug 326798 for future plans to switch over to strict spec compliance in Virgo at an appropriate version boundary.
I have documented the current behaviour in the "Known Issues" section of the Programmer Guide. See commit d4d654b10679a963a87f0cb0d5519b6f4595dac6 on the 2.1.x branch of the documentation repo for details.
