• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Rob Spoor
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Carey Brown
Bartenders:

Spring in Action Question/Jakarta EE

 
Ranch Hand
Posts: 493
9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Could you please discuss any similarities and/or differences between the Spring approach versus the Jakarta EE approach?  For example, doesn't Spring always have the disadvantage of continually needing to catch up to the latest Java (and/or Jakarta EE) specifications?  Or are both technologies evolving and "learning from each other" over time?  Are there certain areas of Jakarta EE that Spring will never "catch up" to?  
 
Saloon Keeper
Posts: 26534
187
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have been using Spring in a Java Enterprise environment since it was J2EE. I never considered it an either/or situation. Spring Data makes an excellent backend for JavaServer Faces webapps. I've used Spring features like Spring Batch, Scheduling, and email services as well.

In any event, chances are you'll find people from Spring involved in the Jakarta JSR processes and Spring has always been kept aggressively up to date.
 
author
Posts: 422
13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In short, where it makes sense, Spring will leverage work done in other projects, including JakartaEE.

That said, Jakarta EE as a whole attempts to create its own mega-framework that can be seen as competing with Spring. To be honest, I've not had much opportunity to consider Jakarta EE as a whole lately. What I do know and believe is that Spring is moving faster, covers more ground, and is more innovative than what I've seen in Jakarta EE. I don't say that to pick a fight...if you or anyone disagrees, then that's fine and I won't be dragged into a Jakarta EE vs. Spring debate. I'm just saying that from what I've seen and experienced, Spring is the best choice for enterprise and cloud development.
 
Charles O'Leary
Ranch Hand
Posts: 493
9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks Tim and Craig.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic