[ee4j-community] Just for application servers?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[ee4j-community] Just for application servers?

From: Jean-Francois James <jefrajames@xxxxxxxxx>
Date: Wed, 11 Oct 2017 15:29:46 +0200
Delivered-to: ee4j-community@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/ee4j-community>
List-help: <mailto:ee4j-community-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/ee4j-community>, <mailto:ee4j-community-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/ee4j-community>, <mailto:ee4j-community-request@eclipse.org?subject=unsubscribe>

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

Follow-Ups:
- Re: [ee4j-community] Just for application servers?
  - From: David Blevins
- Re: [ee4j-community] Just for application servers?
  - From: Martijn Verburg

Prev by Date: Re: [ee4j-community] EE4J and the JCP
Next by Date: Re: [ee4j-community] Just for application servers?
Previous by thread: [ee4j-community] EE4J and the JCP
Next by thread: Re: [ee4j-community] Just for application servers?
Index(es):
- Date
- Thread

Breadcrumbs