Thanks Raghu, I will try to make this clear.
Gemini Project leads: Unless their are any objections I will make the changes I have outlined below with the following text.Gemini (Enterprise Modules Project)
The Gemini project is all about modular implementations
of Java EE technology. It is a collection of implementations of some of the OSGi Enterprise specifications. Each sub-project is a separate and standalone project that provides unique functionality. They can be used in isolation, in combination or with other OSGi bundles to compose a desired OSGi runtime. Brief outlines of each sub-project are below, please visit the sub-projects' pages for more detailed information. All sub-projects share the Gemini Forum for discussions.Gemini Blueprint
The reference implementation of the OSGi Blueprint Service defined in chapter 121 of the OSGi 4.2 Enterprise Specification.
This project was originally called Spring DM before being donated to Eclipse and becoming Gemini Blueprint.
Implements the JMX Management Model Specification defined in chapter 124 of
OSGi 4.2 Enterprise Specification. It provides a set of MBeans that
allows for the administration of an OSGi runtime, the framework and its
bundles and services, over JMX.
Provides modularized distributions of JDBC drivers
suitable for running in OSGi.
It provides an OSGi Service
so that bundles can import and access features
of the driver without having to package the driver within their own bundles. Defined in chapter 125 of the
OSGi 4.2 Enterprise Specification.Gemini Naming
Implements support for Java Naming and Directory Interfaceâ within an OSGi environment as defined by the JNDIâ services specification in chapter 126 of the
OSGi 4.2 Enterprise Specification.Gemini JPA
A modular implementation of Java Persistence API (JPA) service specification defined in chapter 127 of
OSGi 4.2 Enterprise Specification.
This project supports the
OSGi JPA service specification approach that enables clients to use JPA in an OSGi framework.
Gemini Web is the Reference Implementation of the Web
Applications Specification from the OSGi Alliance, defined in chapter
128 of the
OSGi 4.2 Enterprise Specification. It provides support for running enterprise web applications within an OSGi framework.
"Raghuram Devarakonda" <draghuram@xxxxxxxxx>To:
"Gemini and sub-projects developer discussions" <gemini-dev@xxxxxxxxxxx>Sent:
Tuesday, 26 June, 2012 4:29:21 PMSubject:
Re: [gemini-dev] Gemini Home Page
I would like to suggest the following two things in any new text.
1) Emphasize the difference between "Gemini Blueprint" and "OSGi Blueprint". It is easy to gloss over and conflate these two if the difference is not explicitly highlighted (at least, I did).
2) Mention that Gemini blueprint is the new "Spring DM".
On Mon, Jun 25, 2012 at 10:58 AM, Chris Frost <frostc@xxxxxxxxxx>
I answered a forum questions last week from a new OSGi user and they were generally quite confused about the difference between Gemini, Virgo, Spring, Aries and so on. They made the good point that the Gemini home page could be better at explaining things. I'd like to have a go at updating it unless anyone objects. I'm thinking of removing the header as the download, community etc.. pages just link to each of the sub-projects. Moving links to things like forums and mailing lists to the side bar and in the main body putting in a new overview of Gemini and a short paragraph about each project with a link to their respective home pages.
If no one objects I'll put some text on here and then move it to the website if everyone is happy. Hopefully all this in time for the next Gemini call.
Christopher Frost - VMware
Virgo from EclipseRT
gemini-dev mailing list
gemini-dev mailing list