3 ms·
> It's been around longer than Jakarta Not really, Jakarta came from Java EE, which came from J2EE, which was released early 2000. Spring is from 2003 and star
by henk53 4y ago
> It's been around longer than Jakarta
Not really, Jakarta came from Java EE, which came from J2EE, which was released early 2000. Spring is from 2003 and started essentially as a framework for J2EE.
> and influenced it a lot.
It goes both ways.
Spring for instance started calling code "configuration" and wanted us to put it in huge amounts of XML. Java EE started with using annotations for bean definition and injection. Spring was initially against this idea, arguing configuration should be external and not embedded in the code. Citing that you would otherwise needed to recompile your code in order to change configuration.
Many years later Spring projects barely use those huge XML files anymore and its all autowire.
- invalidname 4y agoNot really. J2EE has been around for a while. But it was RADICALLY different and was pretty much horrible. Then it copied many of the AOP aspects of Spring (inject etc) as it evolved. The current standard of Jakarta looks more like Spring than its original form. As such most of the implementations of the standard are much newer. So yes, the standard origins are old but that's not a relevant metric. I said, cross pollination. E.g. just recently the Spring Native example is totally an example of Spring copying a great idea from the Quarkus et al.