Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] Are there no requirements for Innovation?
My POV:

JakartaEE (don’t know much about CXF) is standards/specifications https://jakarta.ee/specifications/ 
To make sure your application works per-JakartaEE standards, it needs to follow/implement (say) A,B,C rules. 

JakartaEE (and most standards) define these A, B, C rules and leave the implementation details to the implementor. 

As an implementor, develop your software to conform to A,B,C to be JakartaEE Complaint + do whatever on top of it (your innovations). Obviously the better your innovations/makes things easy/simple for users the more adaptable your product/service is. 

As an example: All the below are servlet containers + (additional features): Apache Tomcat, Jetty, Weblogic, Helidon  

Thanks
Suren

On Sun, Apr 26, 2020 at 5:53 AM Mihai A. <amihaiemil@xxxxxxxxx> wrote:
Hi All,

I know I may be late to the party with the following question, but it just struck me the other day: are there no innovation requirements for certifying a platform as Jakarta EE compatible?

Looking at what we have now, it seems to me that all I have to do is take Glassfish, rebrand it and bam: I have my own certified Jakarta EE platform.

Or take Apache CXF and other bits and pieces implementing the required specs, put them together under a new brand and again, jackpot!

Shouldn't there be a requirement for a minimum of actual implementation effort?
Or maybe there are such requirements and I'm not aware of them...

Best regards,
Mihai
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community

Back to the top