Skip to main content

Maya (3.0) Release Candidate 1 - Release Notes

Release Candidate 1 of Virgo Maya (3.0) finally brings the snaps framework for modular web applications out of prototype status. The separate snaps download includes a completely new "Virgo Snaps User Guide" (also available online) and a comprehensive sample application. The User Guide describes how to install snaps on top of Virgo Tomcat Server and uses the sample application to verify the installation and step through all the major features of snaps.

RC1 also provides significant improvements to the rest of Virgo. It improves the performance of resource lookups for web applications, upgrades the version of Gemini Web to 2.0.0.RC1, moves the Web Integration Layer configuration from config/ to repository/ext/, provides a way of disabling the console telnet and ssh ports and disables them by default (see the User Guide section "Enabling Equinox Console"), and fixes several bugs.

The document "Creating an Application with Virgo" has being replaced with a "Guide to the GreenPages Sample" which will appear in the next GreenPages release. Meanwhile, some material from "Creating an Application with Virgo" which was more germane to the User and Programmer Guides has been moved to those documents in RC1.

RC1 represents a bug freeze for Virgo 3.0. Unless critical bugs are found in RC1, the only changes before 3.0 is released will be in documentation.


  • Bug 343346: Slow JSP compilation.
  • Bug 352575: config/ is superseded by repository/ext/
  • Bug 350846: [Gogo] Need a way of disabling a console port in the console configuration file.

A full list of bug fixes included in this release candidate is available here.

Incubator Bundles

Note that two bundles included from the Equinox components component are in incubation status.

The Region Digraph bundle was moved from Virgo into Equinox incubation, but is otherwise in a stable, well-tested state.

The Console Supportability bundle, which integrates the Apache Felix Gogo shell, is in incubation status mainly because it depends on interfaces that were being worked on in the OSGi Alliance. However, the Alliance has decided not to continue that particular piece of specification work since Gogo is already proving to be a popular, reusable console.

Back to the top