Jump to: navigation, search

Difference between revisions of "Virgo/Future"

(Release Branding)
m (Table looks better)
Line 89: Line 89:
 
To accommodate simultaneous releases of Virgo runtime, OSGi Web Container runtime, and Virgo tooling, we are branding each release with the name of a colour, including old releases.  
 
To accommodate simultaneous releases of Virgo runtime, OSGi Web Container runtime, and Virgo tooling, we are branding each release with the name of a colour, including old releases.  
  
{| width="600" border="1" cellpadding="1" cellspacing="1"
+
{| class="wikitable" border="1" cellpadding="10" cellspacing="0"
|+ Virgo Release Branding
+
|+ '''''Virgo Release Branding'''''
 
|-
 
|-
| Brand
+
! Brand  
| Runtime
+
! Runtime
| Web Container
+
! Web Container  
| Eclipse IDE Tooling
+
! Eclipse IDE Tooling  
 
|-
 
|-
| Fern
+
| Fern || SpringSource dm Server 1.0 || - || -
| SpringSource dm Server 1.0
+
| -
+
| -
+
 
|-
 
|-
| Emerald
+
| Emerald || SpringSource dm Server 2.0 || OSGi Web Container 1.0 || -
| SpringSource dm Server 2.0
+
| OSGi Web Container 1.0
+
| -
+
 
|-
 
|-
| Cornflower
+
| Cornflower || Virgo 2.1 || Gemini Web 1.1 || -
| Virgo 2.1
+
| Gemini Web 1.1
+
| -
+
 
|-
 
|-
| Maya
+
| Maya || Virgo 3.0 || Gemini Web 2.0 || -
| Virgo 3.0
+
| Gemini Web 2.0
+
| -
+
 
|-
 
|-
| Bondi
+
| Bondi || Virgo 3.5 || Gemini Web 2.1 || Virgo IDE 1.0? - TBD
| Virgo 3.5
+
| Gemini Web 2.1
+
| Virgo IDE 1.0? - TBD
+
| -
+
 
|-
 
|-
| Sky
+
| Sky || Virgo 3.6 or 4.0 || Gemini Web 2.1 or 2.2 || Virgo IDE 1.0? - TBD
| Virgo 3.6 or 4.0
+
| Gemini Web 2.1 or 2.2
+
| Virgo IDE 1.0? - TBD
+
 
|}
 
|}
  

Revision as of 07:03, 27 September 2012


This page summarises the Virgo plan and notes design ideas for future Virgo features.

Virgo Plan

The following plan is subject to change and depends on how much resource is available as the project evolves.

3.0.0 (Maya) Release

Theme: Eclipse RT integration

Schedule: July/August 2011

Draft Release Notes for 3.0.0

Content:

  • Jetty support (bug 321726)
  • Use Equinox config admin instead of that of Felix (bug 310217)
  • Use Equinox log service instead of that of Felix (bug 310218)
  • Use Equinox event admin instead of that of Felix (bug 310219)
  • Upgrade Spring to 3.0.5 (bug 314282)
  • Rebase region support on OSGi framework hooks (bug 330776)
  • Tomcat 7/servlet 3.0 (bug 332045)
  • Make Virgo's web behaviour conform strictly to the OSGi web spec (bug 326798)
  • Support OSGi Log service (bug 342716)
  • Move the Kernel to DS to remove the fixed startup order (bug 333474)
  • Allows PARs to contain plans (bug 335689)
  • Remove entry/exit advice from hashCode() equals() and toString() methods (bug 328033)
  • Critical bug fixes

Required CQs

5094 APPROVED Tomcat 7.0.12 Version: 7.0.12

5095 APPROVED Tomcat 7.0.12 Version: 7.0.12 (PB CQ5094)

5012 APPROVED Java Unified Expression Language Version: 2.2

5014 APPROVED javax.annotation Version: 1.1

5083 APPROVED Apache Felix Gogo Version: 0.8.01

5092 APPROVED org.apache.mina.core Version: 2.0.2

5091 APPROVED Apache SSHD Version: 0.5.0

4462 APPROVED javassist Version: 3.13.0.GA

3.5.0 (Bondi) Release

Theme: p2 and tooling integration

Schedule: July 2012

Draft Release Notes for 3.5.0

Content:

  • Provision Virgo with p2 (bug 343543)
  • Virgo distribution based on p2 provisioning - Virgo Nano (bug 364571)
  • Upgrade from Spring DM to Gemini Blueprint (bug 317943)
  • Become a release train project (bug 374214)
  • Support for Virgo IDE tooling
  • Critical bug fixes

Required CQs

List of required CQs - approved

Nice to Have

The following items currently do not fit in the above plans, but have been raised as desirable by one or more users:

  • Admin console administration of remote Virgo instances
  • Multiple user regions

Future Releases

The following features are not currently in plan:

  • p2 repository in the repository chain (bug 309778)
  • Support Java enterprise APIs(EJB, CDI, JPA, JSF, Web)
  • Integration server
  • Batch server

Release Branding

To accommodate simultaneous releases of Virgo runtime, OSGi Web Container runtime, and Virgo tooling, we are branding each release with the name of a colour, including old releases.

Virgo Release Branding
Brand Runtime Web Container Eclipse IDE Tooling
Fern SpringSource dm Server 1.0 - -
Emerald SpringSource dm Server 2.0 OSGi Web Container 1.0 -
Cornflower Virgo 2.1 Gemini Web 1.1 -
Maya Virgo 3.0 Gemini Web 2.0 -
Bondi Virgo 3.5 Gemini Web 2.1 Virgo IDE 1.0? - TBD
Sky Virgo 3.6 or 4.0 Gemini Web 2.1 or 2.2 Virgo IDE 1.0? - TBD

Note 1: the following "wimp list" of colours that we are steering clear of: Azure, Indigo.

Note 2: the SpringSource dm Server releases are shade of green because of the SpringSource branding. Virgo has cornflower blue in its logo and admin console styling, so we chose shades of blue for Virgo releases.

Future Features

Jetty Support

This is covered by bug 321726. The full design and the current status can be found on the Jetty Web Container page.

Prototypes

Snaps

Snaps is a prototype also from dm Server where it was known as Slices. It aims to give you the full benefit of a dynamic and modular OSGi environment for your web applications by allowing you to spread the front end across many bundles, or Snaps. The Snaps source code is available from one of our Git repos listed on the 'Source' tab. Thanks to Patsy Phelan and Dmitry Sklyut for comments on this content.

A Snap is an OSGi Web Application Bundle that is responsible for handling requests for part of the total application. Requests are served up to each snap depending on what part of the context path the snap has registered to handle. Each Snap will be given requests by a host bundle. A Host bundle is also just a normal web application bundle with filter configured to dispatch certain requests to any registered Snaps.

  Snaps.png

The host will handle requests to '/app/*' while '/app/orders' and '/app/billing' will be dispatched to the relevant Snap bundle.

Snaps is different from other technologies such as Web Fragments in that it much more decoupled and takes advantage of OSGi to allow for the dynamic composition of a web app at runtime. The lifecycle of the Snap and the Host is completely decoupled. This is due to the services like approach. Web Fragments are static and much more closely coupled, they share the same classpath and the modularity it offers is only at development time. This extra decoupling means that snaps can be developed in isolation from the host application, even after the host application has be released.

OSGi Explorer

See OSGi Explorer.