[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] Eclipse Jetty and EE4J
|
The absence of an RI and clearly delineated specification leads is an interesting approach indeed. It would be very good to hear end-user community feedback on this approach. Personally I liked these aspects of how Sun/JCP did things for several key reasons:
* You were guaranteed at least one working, compatible implementation with the specification.
* If there was any ambiguity, you could look at the RI for likely specification lead intent.
* You knew who was clearly responsible for specification delivery, following due process, resolving differences of opinion, ensuring transparency and at least listening to community feedback.
Whatever the weaknesses of this approach, at least it is something the community knows how to deal with (including complete absense and non responses from the specification lead).
The downsides of the alternative is basically unknown. The worst case is a situation where no one is responsible for anything because no one feels ownership of anything. A very close second situation of concern would be a narrow group of contributors that is not very responsive, flexible or transparent. I think many of us have seen these situations first hand in OSS projects that do not follow the Sun/JCP model.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Dimitris Andreadis <dandread@xxxxxxxxxx>
Date: 10/13/17 5:44 AM (GMT-05:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>, Greg Wilkins <gregw@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Eclipse Jetty and EE4J
The absence of an RI is an interesting approach, i.e. if the Spec
is complete enough to not have to look into the RI to understand
under-specified aspects.
How about interop testing that is now performed against the RI?
Should you be able to pick any other opernsource implementation
and test against it, to claim compliance?
/Dimitris
Dimitris Andreadis
Senior Engineering Manager
Red Hat JBoss EAP/WildFly
On 13/10/2017 03:42, Greg Wilkins
wrote:
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community