Difference between revisions of "Virgo/Future"

From Eclipsepedia

Jump to: navigation, search
(3.0.0 Release)
(42 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Virgo}} This page summarises the Virgo plan and notes design ideas for future Virgo features.  
+
{{Virgo}}
 +
This page summarises the Virgo plan and notes design ideas for future Virgo features.  
  
 
= Virgo Plan  =
 
= Virgo Plan  =
Line 5: Line 6:
 
The following plan is subject to change and depends on how much resource is available as the project evolves.  
 
The following plan is subject to change and depends on how much resource is available as the project evolves.  
  
== 3.0.0 Release ==
+
== 3.7.0 (Steel) Release ==
  
Theme: Eclipse RT integration
+
* TBD, but see the [https://bugs.eclipse.org/bugs/show_bug.cgi?id=396813 Steel bugtrain bug 396813].
  
Schedule: June 2011
+
== Release Branding  ==
  
Draft [[Release Notes for 3.0.0]]
+
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.  
  
Content:
+
{| class="wikitable" border="1" cellpadding="10" cellspacing="0"
 +
|+ '''''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 3.5
 +
|-
 +
| Sky || Virgo 3.6 || Gemini Web 2.2 || -
 +
|-
 +
| Steel || Virgo 3.7 || Gemini Web 2.2 or 2.3 || -
 +
|}
  
*Jetty support ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=321726 bug 321726])
+
Note 1: we are steering clear of the following "wimp list" of colours: [http://www.microsoft.com/windowsazure/ Azure], [http://www.eclipse.org/indigo/ Indigo].
*Use Equinox config admin instead of that of Felix ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=310217 bug 310217])
+
*Use Equinox log service instead of that of Felix ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=310218 bug 310218])
+
*Use Equinox event admin instead of that of Felix ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=310219 bug 310219])
+
*Upgrade Spring to 3.0.5 or later ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=314282 bug 314282])
+
*p2 repository in the repository chain ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=309778 bug 309778])
+
*Rebase region support on OSGi RFC138 ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=330776 bug 330776])
+
*Tomcat 7/servlet 3.0 ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=332045 bug 332045)]
+
* Make Virgo's web behaviour conform strictly to the OSGi web spec ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=326798 bug 326798])
+
*Support OSGi Log service ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=342716 bug 342716])
+
*Move the Kernel to DS to remove the fixed startup order ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=333474 bug 333474])
+
*Allows PARs to contain plans ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=335689 bug 335689])
+
*Remove entry/exit advice from hashCode() equals() and toString() methods ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=328033 bug 328033])
+
*Critical bug fixes
+
  
=== Required CQs  ===
+
Note 2: the SpringSource dm Server releases are shades 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.
  
[https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5094 5094] awaiting_committer P3 new emo-ip-... NEW Tomcat 7.0.12 Version: 7.0.12
+
= Future Directions =
  
[https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5095 5095] new P3 new emo-ip-... NEW Tomcat 7.0.12 Version: 7.0.12 (PB CQ5094)  
+
Support for the OSGi Subsystems specification is deferred indefinitely ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=358437#c4 rationale]), except for [https://bugs.eclipse.org/bugs/show_bug.cgi?id=358441 generalising the InstallArtifact tree to a DAG] which was implemented in Virgo 3.5.0 (see the Kernel Enhancements section of the [http://www.eclipse.org/virgo/download/release-notes/3.5.0.RELEASE.php Virgo 3.5.0 release notes]).
 
+
[https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5012 5012] new P3 new emo-ip-... APPROVED Java Unified Expression Language Version: 2.2
+
 
+
[https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5014 5014] new P3 new emo-ip-... APPROVED javax.annotation Version: 1.1
+
 
+
[https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5083 5083] new P3 new emo-ip-... APPROVED Apache Felix Gogo Version: 0.8.01
+
 
+
[https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5092 5092] new P3 new emo-ip-... NEW org.apache.mina.core Version: 2.0.2
+
 
+
[https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5091 5091] new P3 new emo-ip-... NEW Apache SSHD Version: 0.5.0  
+
 
+
[https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4462 4462] awaiting_analysis P3 new emo-ip-... APPROVED javassist Version: 3.13.0.GA
+
 
+
=== Nice to Have  ===
+
 
+
The following items currently do not fit in the 3.0 plan, but have been raised as desirable by one or more users:
+
 
+
*Upgrade from Spring DM to Gemini Blueprint ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=317943 bug 317943])
+
*Admin console administration of remote Virgo instances
+
*Multiple user regions
+
 
+
== Future Releases  ==
+
 
+
The following features are not currently in plan:
+
 
+
*Integration server
+
*Batch server
+
 
+
= Future Features  =
+
 
+
== Jetty Support  ==
+
 
+
This is covered by [https://bugs.eclipse.org/bugs/show_bug.cgi?id=321726 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.
+
 
+
  [[Image: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.
+
 
+
[[Category:Virgo]] [[Category:EclipseRT]]
+

Revision as of 05:51, 18 December 2012


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

Contents

Virgo Plan

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

3.7.0 (Steel) Release

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 3.5
Sky Virgo 3.6 Gemini Web 2.2 -
Steel Virgo 3.7 Gemini Web 2.2 or 2.3 -

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

Note 2: the SpringSource dm Server releases are shades 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 Directions

Support for the OSGi Subsystems specification is deferred indefinitely (rationale), except for generalising the InstallArtifact tree to a DAG which was implemented in Virgo 3.5.0 (see the Kernel Enhancements section of the Virgo 3.5.0 release notes).