More specifically, is Red Hat going to continue to move CDI and Bean Validation forward? What about JPA? I don't think anyone in the community can realistically move that forward. I have similar concerns for Servlet (and perhaps a more reactive alternative to Servlet). These APIs are so complex that you really need dedicated folks that work for a vendor full time to move them forward.
Reza, yes, Red Hat plans to move CDI and Bean Validation forward. Mark’s comments were geared more towards Oracle’s decision to “Open Up” the Java EE and the large number of JSRs they currently lead.
-------- Original message -------- Date: 10/12/17 7:44 AM (GMT-05:00) Subject: Re: [ee4j-community] Red Hat committment to EE4J
Mark, For the avoidance of doubt and for those who haven't been paying
attention :) Red Hat is committed to working for the continuing
success of Java EE and now EE4J. We intend to put forward various
individuals who may be relevant to lead various JSRs if no other
appropriate community members step forward as well as the JSRs we lead
currently. When the time is right (note, when not if) we'll also work
to ensure EE4J and Eclipse MicroProfile collaborate in a meaningful
manner and hopefully "merge" in whatever way is appropriate and
determined by both communities.
I'm assuming that the last "we" here is the MicroProfile community and not RedHat, correct?
Mark.
_______________________________________________
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
_______________________________________________ ee4j-community mailing list ee4j-community@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-community
|
