[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] Charter Feedback
|
I too agree profiles are a very valuable concept and goes extremely well with the notion of ground-up modularity. Perhaps there is a way to mention both concepts together in the charter?
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Josh Juneau <juneau001@xxxxxxxxx>
Date: 10/7/17 10:25 AM (GMT-05:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Charter Feedback
I agree with all comments made in this discussion...+1.
I am a little surprised that the project charter does not reference the development and/or support of multiple EE4J profiles, such as Java EE has today. At this time, one has the opportunity to choose between using the Java EE web profile or the full umbrella for a project. Vendors and cloud/microservices implementations also can be Java EE compliant with one or both of these profiles. I hope that EE4J will adopt similar profile model, carrying forward what is available in Java EE and even building upon it. I had always hoped that Java EE would branch out into even more profiles, specifically having one that was geared towards cloud/microservices, such as MicroProfile. Maybe the idea of profiles goes away and EE4J just becomes a modular platform, allowing one to utilize any specifications that are required for their application?
Just thought it may be helpful to have a bullet point around multiple profiles somewhere in the charter.
Thanks