[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] [jetty-dev] [rt-pmc] Draft graduation/release review docuware for Virgo and Gemini Web
- From: "O'Flynn, Dennis" <Dennis.OFlynn@xxxxxxxxxxxxx>
- Date: Fri, 24 Sep 2010 09:46:01 -0400
- Delivered-to: email@example.com
- Thread-index: Actb07qmCh9H9jtvST60Uun6p8LAlgAGqcXQ
- Thread-topic: [virgo-dev] [jetty-dev] [rt-pmc] Draft graduation/release review docuware for Virgo and Gemini Web
Re: current plan is to support Jetty in Virgo rather than Gemini Web
What does this mean? I would assume this implies that Jetty would be
used as both the OSGi HttpService as well as the JettyWarDeployer.
Is there any wiki doc or bugz task that I can reference?
[mailto:virgo-dev-bounces@xxxxxxxxxxx] On Behalf Of Glyn Normington
Sent: Friday, September 24, 2010 6:32 AM
To: Jetty @ Eclipse developer discussion list
Cc: Virgo Project; Gemini and sub-projects developer discussions;
Runtime Project PMC mailing list
Subject: Re: [virgo-dev] [jetty-dev] [rt-pmc] Draft graduation/release
review docuware for Virgo and Gemini Web
Thanks Greg. The current plan is to support Jetty in Virgo rather than
Gemini Web. This remains a high priority for the first release following
the baseline (2.1.0) release of Virgo.
On 23 Sep 2010, at 19:32, Greg Wilkins wrote:
> While we do have our own RFC66 implementation, we see that as no
> reason not to be integrated with Gemini and/or Virgo and we stand
> ready to assist either of those projects do the integration that was
> discussed at the time the projects were accepted.
> Unfortunately I don't really know enough about the relationship
> between virgo and gemini to comment on if it best to integrate
> directly in virgo or via Gemini web. I do think that we should do
> one or the other (or both) - not neither. We are happy to follow the
> suggestion of which is best to do.
> On 17 September 2010 00:31, Glyn Normington <gnormington@xxxxxxxxxx>
>> Hi Jeff
>> We originally anticipated supporting Jetty in Virgo by supporting
Jetty in Gemini Web. However, it appears that Jetty has been tracking
RFC 66 and has its own implementation of the OSGi Web Applications
specification. So, from that perspective, it is more natural to consider
Jetty a functional superset of Gemini Web. So we are now proposing to
support Jetty directly in Virgo as an alternative to Gemini Web. Does
this seem reasonable? Maybe Jetty folks would care to comment.
>> On 16 Sep 2010, at 18:48, Jeff McAffer wrote:
>>> Overall they look good. Well done. I did note in the Gemini version
there were no plans listed for enabling Jetty integration. That feels
like the same discussion we had in the Virgo context. I believe it
should be an RT imperative that where there exists a reasonable
implementation at Eclipse, it should be used or usable. We want people
to be able to come to RT and get pieces that fit together and not end up
with N server/database/UI/... technologies.
>>> On 2010-09-16, at 6:10 AM, Glyn Normington wrote:
>>>> I would be grateful for any feedback on the attached draft
>>>> Please note that if Gemini graduates out of incubation before we
need to submit the Gemini Web docuware, we'll be able to drop the
graduation aspects of that docuware.
>>>> rt-pmc mailing list
>>> rt-pmc mailing list
>> rt-pmc mailing list
> jetty-dev mailing list
virgo-dev mailing list