| Re: [jakartaee-platform-dev] [DISCUSS] Include Jakarta Data in EE 11 |
|
Oliver, I hope the following comment that you posted is just a misunderstanding of what has actually gone into the spec vs. what was under discussion but not actually included, > In other words: the problem we see is not the lack of features but the scope already exceeding what's been established in the industry. This would add
more complexity to our projects with no apparent benefits. Given the current state of affairs there are no plans for Spring Data to implement the specification. Regarding the instances you cited of exceeding what vendors currently do: https://github.com/jakartaee/data/issues/109 - It’s true this would have been a major addition that exceeds what vendors do. It was discussed a
lot. It was very contentious with a lot of disagreement over it. Consequently, it never went into the spec. This should not in any way be blocking Spring from implementing Jakarta Data because this proposal isn’t part of Jakarta Data. https://github.com/jakartaee/data/issues/94 - This one confuses me because it’s just an extra annotation that does exactly the same thing that the
OrderBy keyword already does, and I can’t see how something so trivial could cause trouble to Spring Data. Hopefully the real reason was the mistaken belief that 109 had gone into the spec, not this change. There was certainly disagreement on whether this
annotation should be taken out of the spec that went on for some time, I thought we had ultimately resolved it on one of the Jakarta Data calls, which included both Graeme and Otavio (apparently no one from Spring must have been on that particular call).
If this truly does somehow block Spring from implementing Jakarta Data, or if Spring just feels so strongly about it that you would forgo implementing Jakarta Data over it, then we’ll just take it out of the spec for you. Please follow up with me on that
(either one this email chain or separately) and we’ll get it taken care of. |