Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cn4j-alliance] Thoughts on the CN4J purpose

Profiles are not just for developers though. Expanding the number of EE implementations by lowering the bar with a smaller base profile and associated TCK is something we would like to see. Having a profile in EE that revs at a faster pace then the current Web profile and platform are another reason we would like to see a core profile introduced.

On Thu, Jan 14, 2021 at 3:45 AM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:

I don’t think additional Jakarta EE profiles adds a lot for developers. Although it makes it easier for a product creator to gain Jakarta EE compatibility on a subset of specifications. Just looking at our download stats Full profile is download 20x more than Web Profile. Also we get more demands to add additional apis to Payara Micro which is Web Profile+ than anything else.

 

Given we have MicroProfile I don’t see the need to have an equivalent profile in Jakarta EE. Can’t MicroProfile just create a platform TCK that takes a subset of the Jakarta EE TCK for the specs that form that profile.    

 

From: cn4j-alliance <cn4j-alliance-bounces@xxxxxxxxxxx> On Behalf Of Edwin Derks
Sent: 14 January 2021 07:43
To: Discussions on formation of a CN4J Alliance with the MicroProfile Working Group <cn4j-alliance@xxxxxxxxxxx>
Subject: Re: [cn4j-alliance] Thoughts on the CN4J purpose

 

I'm not sure if too "many" profiles are going to be confusing. It's how we make them available. But having vendors implement a profile and add a few other specifications, effectively creating their own vendor-specific profiles might not be the desired way to go either.

 

On agreeing whether or not to evolve Jakarta EE specifications "too much": I don't think we have any choice but to evolve them in order to keep them valuable for developers. If they aren't, we run the risk that vendors are going to create their own versions of these specifications because their end-users aren't going to use the original specifications, effectively rendering them obsolete. If that happens, the whole reason that we have standards in specification falls apart and loses its value.

 

Edwin

 



Back to the top