Re: [jakarta.ee-community] A Composable Platform Over Profiles
I agree. A profile should be limited in scope and it should be possible to combine profiles. In addition, one profile could be an expansion of another. For example, their might be a REST profile which can stand alone. But it could also be a subset of a larger Microprofile.
I do think, however, that we should consider a Jakarta EE “Core”, a minimum common platform, upon which all profiles are based. The reason: You need a core or there really is no platform other than Java SE, and without a core you cannot express how different profiles will impact and interact with each other.
The Jakarta EE Core would be the foundation of future version of a Legacy Profile, a Web Profile, and other profiles. It might include a few or a dozen JSRs like CDI and JMX, for example, but not require many others such as EJB, JAX-WS or JAX-RS. The point here (at this moment) is not to say what specs are in the core, but to argue for a small subset of Java EE as a core.
So Jakarta EE would be comprised of a stable, slowly evolving Core upon which many different profiles can be standardized according to problem domains and those profiles can be supported by vendors in any combination on top of the Core subject to compliance testing.
I argue that a better approach would be to define the platform as a palette of composable standards, where profiles define only what must be available for a developer to choose from, and only limit the version of a given standard to the minimum that must be provided. Under this model there is less of a need to define a perfect profile, since it can be freely adjusted by the developer to fit his or her needs. Instead, all that matters is that we have a sensible array of choice.
Jason T. Greene
Chief Architect, JBoss EAP
jakarta.ee-community mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit