| Re: [jakarta.ee-community] Are there no requirements for Innovation? |
If the rebranding is within the scope of the allowed licensing rules, that should be an allowed platform for certification. I don't see that it is the responsibility of the platform community to dig into the details of the submitted platform for such details and innovation has nothing to do with passing the TCK. There should be as many compatible implementations as the market is willing to bear. Innovation of viability is up to the market place, not the certification process._______________________________________________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
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-community