Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Virgo/Community/Migrating from 2.1.0 to 3.0.0
DRAFT
Contents
XML Schemas
The plan schema has moved to Eclipse.org, ...
Virgo Startup
This is related to the result of bug 333474. Virgo now has dynamic startup - its base bundles do not require ordering anymore. This enables possible usage of other OSGi launchers.
Declarative Service support
This is related to the result of bug 333474. Virgo now supports Declarative services out-of-the-box, both in kernel and the user region.
Virgo Directory Layout
Bug 324991 affects this.
User Region
The following note relate to the likely result of bug 330776.
Rather than the user region being a nested OSGi framework, it is now a collection of bundles in the same OSGi framework as the kernel with isolation controlled by config/org.eclipse.virgo.kernel.userregion.properties.
Framework properties are now specified only in lib/org.eclipse.virgo.kernel.launch.properties (this is subject to change) and must include org.osgi.framework.bsnversion=multiple for correct functioning of the user region.
There is now one OSGi console which can be enabled using the osgi.console framework property. This console can see all the bundles in the framework, although the vsh subcommand is limited to the user region bundles.
Web
- Virgo previously added additional Manifest headers to web application to make them easier to develop. This support is being dropped as it didn't appear in the specification for 'Web Application Containers' (RFC66). The major effect this will have is that you must now include:
- a Bundle-Classpath header for classes in 'WEB-INF/classes'
- package imports for anything the web bundle needs from the System bundle.
- The Module-Type header is no longer used to identify a bundle as a WAB, the presence of a Web-Contextpath header now dose this as per the specification.