Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Just for application servers?

Interestingly enough I think this was the first question/feedback at the EE4J panel at JavaOne.  So you were there in spirit, Jean-François :)


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852

On Oct 11, 2017, at 6:29 AM, Jean-Francois James <jefrajames@xxxxxxxxx> wrote:

First off, I want to thank all of you who've started working on EE4J. What  an exciting and huge challenge!

 

Reading the draft charter, I've the feeling that speaking about "APIs for application servers" is a bit restrictive. The present is focused on microservices and containers, serverless may be the future and in this context "Application servers" in general do not look that future-proof. 

 

By saying that, I don't want to re-start the technical debate "Thin war vs Uber jar". It is just a matter of communication and intention. May be we should speak about "standard APIs for modern Java applications".

 

A good illustration of what I mean here is RedHat Wildfly Swarm wich enables to run the same applications in a server or standalone mode.



Jean-François James

_______________________________________________
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


Back to the top