| Re: [ee4j-community] Red Hat committment to EE4J |
Guess it would also be nice to see Red Hat participating in Areas like Security where Arjan (now at Payara) has contributed to an extent that qualifies him for a possible (Spec) Lead role, but other than Oracle as the current Spec Lead of JSR 375 and a few dedicated Individuals no other company did help with Java EE Security. Werner From: ee4j-community-request@xxxxxxxxxxx Send ee4j-community mailing list submissions to ee4j-community@xxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://dev.eclipse.org/mailman/listinfo/ee4j-community or, via email, send a message with subject or body 'help' to ee4j-community-request@xxxxxxxxxxx You can reach the person managing the list at ee4j-community-owner@xxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of ee4j-community digest..." Today's Topics: 1. Re: Red Hat committment to EE4J (John Clingan) 2. Re: Red Hat committment to EE4J (reza_rahman) ---------------------------------------------------------------------- Message: 1 Date: Thu, 12 Oct 2017 07:01:22 -0700 From: John Clingan <jclingan@xxxxxxxxxx> To: EE4J community discussions <ee4j-community@xxxxxxxxxxx> Subject: Re: [ee4j-community] Red Hat committment to EE4J Message-ID: <94A297E7-A4E6-4734-BD55-74291FF03012@xxxxxxxxxx> Content-Type: text/plain; charset="utf-8" > On Oct 12, 2017, at 6:48 AM, reza_rahman <reza_rahman@xxxxxxxxx> wrote: > > 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 -------- > From: "John D. Ament" <john.d.ament@xxxxxxxxx> > Date: 10/12/17 7:44 AM (GMT-05:00) > To: EE4J community discussions <ee4j-community@xxxxxxxxxxx> > Subject: Re: [ee4j-community] Red Hat committment to EE4J > > Mark, > > On Thu, Oct 12, 2017 at 5:35 AM Mark Little <mlittle@xxxxxxxxxx <mailto:mlittle@xxxxxxxxxx>> wrote: > 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 <mailto: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 <https://dev.eclipse.org/mailman/listinfo/ee4j-community> > _______________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20171012/e908dbc9/attachment.html> ------------------------------ Message: 2 Date: Thu, 12 Oct 2017 10:03:59 -0400 From: reza_rahman <reza_rahman@xxxxxxxxx> To: EE4J community discussions <ee4j-community@xxxxxxxxxxx> Subject: Re: [ee4j-community] Red Hat committment to EE4J Message-ID: <mailman.50.1507824011.15648.ee4j-community@xxxxxxxxxxx> Content-Type: text/plain; charset="utf-8" I agree the alignment is very important. Hopefully this will be discussed soon, whatever the right venue for that discussion is. Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone -------- Original message --------From: John Clingan <jclingan@xxxxxxxxxx> Date: 10/12/17 9:58 AM (GMT-05:00) To: EE4J community discussions <ee4j-community@xxxxxxxxxxx> Subject: Re: [ee4j-community] Red Hat committment to EE4J ?I think its pretty clear to all of us that we do have to figure out how MicroProfile will align with EE4J in the future. Red Hat definitely understands that MicroProfile as a community will define how that alignment happens. On Oct 12, 2017, at 5:22 AM, John D. Ament <john.d.ament@xxxxxxxxx> wrote: Mark, sure, as long as it's clear that the overall direction of Eclipse MicroProfile is up to that community as a whole.? While various members have a say in its direction, anything that happens should be based on consensus. On Thu, Oct 12, 2017 at 8:11 AM Mark Little <mlittle@xxxxxxxxxx> wrote: John, please read the text in the context of the email subject-line. That should answer your question with regards to every "we", "we'll" in the text. Mark. On Thu, Oct 12, 2017 at 12:44 PM, John D. Ament <john.d.ament@xxxxxxxxx> wrote: > Mark, > > On Thu, Oct 12, 2017 at 5:35 AM Mark Little <mlittle@xxxxxxxxxx> wrote: >> >> 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@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@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@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-community -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20171012/c1eb1840/attachment.html> ------------------------------ _______________________________________________ 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 End of ee4j-community Digest, Vol 2, Issue 79 ********************************************* |