Re: [jakarta.ee-community] A Composable Platform Over Profiles

[Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx>]

I think here you are talking about software outside of Jakarta EE showing that they work with a specific Jakarta EE implemenation. That’s a totally different conversation.  We are concerned here with what makes a product a Jakarta EE product, not how other libraries can work with specific Jakarta EE products.

On Mon, May 7, 2018 at 11:55 AM Mrinal Kanti <mrinal.kanti@xxxxxxxxx> wrote:

On Wed, May 2, 2018 at 7:14 PM, Mrinal Kanti <mrinal.kanti@xxxxxxxxx> wrote:

On Wed, May 2, 2018 at 11:39 AM, Jason Greene <jason.greene@xxxxxxxxxx> wrote:

 

Since the standards are backwards compatible, it's typically implementation concerns and not spec version compliance that leads to multiple implementations in the same product (e.g. a product decides to support myfaces and mojarra). 

The specs can also cause incompatibility across servers due to the optional parts specified in a given version of the specs. For example, we had a few incompatibility issues with eclipselink and hibernate even when they implemented the same version of JPA. So its safer for ISVs to certify their products on specific app server and their versions (assuming app servers don't switch spec implementations) rather than certifying them on the JEE versions in general.

-Mrinal

_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community

--

Richard Monson-Haefel
http://twitter.com/rmonson
http://www.tomitribe.com
http://www.tomitribe.io