Re: [ee4j-community] Initial thoughts on where the Payara team can contr

["Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>]

I still see value in having an RI and as that is currently GlassFish I think it has great relevance. Building a new RI would be a major distraction for EE4J.

 

I don’t think Payara Server should be the RI as Payara Server is evolving in ways that are demanded by our customers as ultimately customers pay for our developers. In time these demands may or may not align with features that are needed by an RI. Saying that we now have good knowledge of the GlassFish code base and are happy to contribute fixes and future integrations to make GlassFish reliable and stable and provide a good developer experience.

 

Ultimately the goal of an RI should be the gold standard on how EE4J apis behave and having an open collaboratively developed RI ensures that where this diverges we can all chip in to clarify and fix the behaviour. Also with having an open source TCK we can all fix the test that allowed anomalous or ill-defined behaviour to slip through. That’s why having a vendor neutral, community developed, GlassFish as RI is I feel the best solution.

 

Steve

 

From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Guillermo González de Agüero
Sent: 11 October 2017 12:53
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Initial thoughts on where the Payara team can contribute best.

 

Great to see this commitment from Payara!

 

One thing I've been wondering for some time is wether GlassFish (the application server, not its components) should really be maintained. I sadly doubt the reliability of the latast GlassFish (>4.0) versions and I'm not sure much people actually use it in production Java EE 7 systems.

 

With GlassFish relicensed as EPL, I guess Payara could also get rid of its Oracle license bits and perhaps be promoted as the RI.

 

Would you possibly be interested in discussing such a thing? I'd like to hear some preliminary thoughts on that matter.

 

 

Regards,

 

Guillermo González de Agüero

 

El mié., 11 de octubre de 2017 20:13, Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> escribió:

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

 

 

_______________________________________________
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