| Re: [ee4j-community] IBM supports the move of Java EE to the Eclipse Foundation |
Kevin, Thanks for highlighting that. I guess "Open Java EE" at the time was more of a codename now found to be EE4J instead? IBM also leads the Portlet Spec. Which not part of Java EE as such (like MVC or JCache) still makes heavy use. Portlet 3.0 added stronger CDI support or AJAX functionalities to make Portal apps more "reactive". Under the right circumstances such specs and JSRs should be optional add-ons and extensions to a core platform. So some may chose JSF, others MVC and again others (with a few different UI frameworks including JSF) could even require the full functionality of a Portlet container. Portlet Bridge for JSF was btw. The very first JSR that Oracle handed control over to another EG member (Liferay) And in discussions between the Liferay reps and new Spec Leads of the Portlet Bridge with Ivar it also must have acted a bit as an inspiration for doing the same with MVC. Two domino pieces that now caused a chain reaction with all of Java EE. 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. Initial thoughts on where the Payara team can contribute best. (Steve Millidge (Payara)) 2. Re: Initial thoughts on where the Payara team can contribute best. (Mike Milinkovich) 3. Re: Initial thoughts on where the Payara team can contribute best. (Edward Burns) 4. IBM supports the move of Java EE to the Eclipse Foundation (Kevin Sutter) ---------------------------------------------------------------------- Message: 1 Date: Wed, 11 Oct 2017 18:13:00 +0000 From: "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx> To: "ee4j-community@xxxxxxxxxxx" <ee4j-community@xxxxxxxxxxx> Subject: [ee4j-community] Initial thoughts on where the Payara team can contribute best. Message-ID: <HE1PR03MB1787AE116921471EB2FAA206914A0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii" Hi All, As EE4J starts to happen and project and code starts to move to the Eclipse Foundation it is now time for the community to put their hand up and indicate which areas people can commit expertise and real development hours to drive forward. We've had some initial discussions on where the Payara team can provide the biggest impact. First and foremost we can take on driving forward GlassFish as the reference implementation, providing key development effort to ensure EE4J GlassFish is free of bugs and integrates new and updated specifications for future EE4J releases as well as assisting in setting up the dev and CI environments for passing the TCK. This will also include helping keep a bunch of the dependent sub-projects that are not JSRs up to date including HK2, Grizzly, CORBA, etc. This is a big piece of work where our knowledge of the code base means we can provide a great contribution. In a couple of other areas we can draw and build on the experience and expertise of Arjan Tijms and provide leadership and sustained developer hours to drive forward JSF with Mojarra as well as JSR 375 along with Soteria the RI. Longer term as project teams are drawn up I imagine we will also take on contributing development to many other EE4J projects and maintenance of RIs. All in all this is an exciting and challenging time that needs community developers, vendors, end users and open-source projects to commit real coding time to the future development of EE4J. I hope we can do our bit without being overwhelmed with the volume of work involved. These are our first thoughts and will evolve as everything becomes clearer. Steve Millidge Payara -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20171011/fabba774/attachment.html> ------------------------------ Message: 2 Date: Wed, 11 Oct 2017 14:15:15 -0400 From: Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> To: ee4j-community@xxxxxxxxxxx Subject: Re: [ee4j-community] Initial thoughts on where the Payara team can contribute best. Message-ID: <62a8764b-fcbe-ad95-df26-a268a79530ce@xxxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="windows-1252"; Format="flowed" Steve, Many thanks. We are looking forward to Payara's contributions to this new community! On 2017-10-11 2:13 PM, Steve Millidge (Payara) wrote: > > Hi All, > > As EE4J starts to happen and project and code starts to move to the > Eclipse Foundation it is now time for the community to put their hand > up and indicate which areas people can commit expertise and real > development hours to drive forward. > > We?ve had some initial discussions on where the Payara team can > provide the biggest impact. First and foremost we can take on driving > forward GlassFish as the reference implementation, providing key > development effort to ensure EE4J GlassFish is free of bugs and > integrates new and updated specifications for future EE4J releases as > well as assisting in setting up the dev and CI environments for > passing the TCK. This will also include helping keep a bunch of the > dependent sub-projects that are not JSRs up to date including HK2, > Grizzly, CORBA, etc. This is a big piece of work where our knowledge > of the code base means we can provide a great contribution. > > In a couple of other areas we can draw and build on the experience and > expertise of Arjan Tijms and provide leadership and sustained > developer hours to drive forward JSF with Mojarra as well as JSR 375 > along with Soteria the RI. Longer term as project teams are drawn up I > imagine we will also take on contributing development to many other > EE4J projects and maintenance of RIs. > > All in all this is an exciting and challenging time that needs > community developers, vendors, end users and open-source projects to > commit real coding time to the future development of EE4J. I hope we > can do our bit without being overwhelmed with the volume of work > involved. These are our first thoughts and will evolve as everything > becomes clearer. > > Steve Millidge > > *Pa* > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20171011/b9d8c778/attachment.html> ------------------------------ Message: 3 Date: Wed, 11 Oct 2017 11:45:30 -0700 From: Edward Burns <edward.burns@xxxxxxxxxx> To: EE4J community discussions <ee4j-community@xxxxxxxxxxx> Subject: Re: [ee4j-community] Initial thoughts on where the Payara team can contribute best. Message-ID: <23006.26314.956118.696295@xxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset=us-ascii >>>>> On Wed, 11 Oct 2017 18:13:00 +0000, "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx> said: [...] SM> In a couple of other areas we can draw and build on the experience SM> and expertise of Arjan Tijms and provide leadership and sustained SM> developer hours to drive forward JSF with Mojarra as well as JSR 375 SM> along with Soteria the RI. Longer term as project teams are drawn up SM> I imagine we will also take on contributing development to many SM> other EE4J projects and maintenance of RIs. Having worked with Arjan and his colleague Bauke Scholtz to extend JSF for several years now, both inside and outside the JCP, I can happily endorse him for that role. However, in the spirit of leaving maximum self determination to the Eclipse Foundation regarding the leadership of constituent technologies, I must point out that I am aware of at least one other party that might want take the con on JSF. I will reach out to those party(ies) out-of-band and recommend they align behind Arjan, but point out that the decision really lies with the EE4J Eclipse leadership. [...] Ed -- | 31 business days until CodeEurope Poland 2017 | 77 business days until JavaLand 2018 | edward.burns@xxxxxxxxxx | office: +1 407 458 0017 ------------------------------ Message: 4 Date: Wed, 11 Oct 2017 14:17:46 -0500 From: "Kevin Sutter" <sutter@xxxxxxxxxx> To: "EE4J community discussions" <ee4j-community@xxxxxxxxxxx> Subject: [ee4j-community] IBM supports the move of Java EE to the Eclipse Foundation Message-ID: <OFA2D16BBE.54FCAE2D-ON862581B6.00675F5D-862581B6.0069FF73@xxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii" Hi, Although I have been active in the various email discussions and voiced my support at JavaOne this past week, I thought it might be good to post explicit support of this move and indicate our continued involvement in the EE4J activities. In case you missed it, IBM announced their support of "Open Java EE" at our Community Keynote last week at JavaOne: http://video.oracle.com/detail/videos/most-recent/video/5600375079001/ibm-javaone-keynote-10-5-2017 IBM has been an active participant in many of the Java EE expert groups in the past and we plan to continue to participate in similar "expert groups" under the Eclipse umbrella. We have also identified a few key technologies that we feel are instrumental to the success of Java microservices -- jax-rs, json-b, json-p, and security. If the EE4J community does not produce or nominate leaders for these technologies, then we would be happy to provide a leadership role. Regardless, we will continue to participate in these respective communities (and several others). And, of course, IBM will continue to lead the Java Batch efforts. Java Batch is currently developed and maintained in a github repo under the Apache v2 license. Since the main goal of the EE4J effort is to initially get Java EE to an open-governance model, the focus will be to first get the Oracle artifacts moved over to EE4J. Once this process is established and is moving forward, then we will consider moving Java Batch as well. Since all of the Java Batch artifacts (including the TCK) are already Apache v2 licensed, the move to Eclipse is not as urgent or immediate. As many of you know, we have also been very instrumental in the MicroProfile efforts -- both from a leadership as well as technical contribution perspectives. We will continue to drive the MicroProfile efforts in parallel with the EE4J efforts. As Ian put it in the video above, EE4J is moving in next door to MicroProfile. Once EE4J becomes established, I'm sure we will need to evaluate the future direction of MicroProfile. Do we continue with MicroProfile as the innovative arm of EE4J? Or, does it meld under the EE4J umbrella? We need to take a wait-and-see view on this direction. And, that's why we won't sit idle with the MicroProfile efforts. We are continuing to define new specifications for inclusion in future versions of MicroProfile. We look forward to this EE4J effort and will continue to work with both Eclipse and Oracle (and the other partners) during this process. --------------------------------------------------- Kevin Sutter STSM, MicroProfile and Java EE architect e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter phone: tl-553-3620 (office), 507-253-3620 (office) LinkedIn: https://www.linkedin.com/in/kevinwsutter -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20171011/4cdeb8bf/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 72 ********************************************* |