Java EE vs Spring

Have you ever wondered what stack to choose in order to build your Web Application from A to Z.
Did you think about using Java EE? Are you confused? Why? Did they advocate Spring Framework to you? Spring is  a great Java Framework but well, there’s an answer summed up by a great blog post from Arun Gupta (Oracle Engineer).
Java EE 6 underwent several high and low level improvements to ease life for application development while being robust and lightweight.
Some of the features of Java EE 6:

  • Adding @Stateless on a POJO makes it an EJB
  • EJBs can be packaged in a WAR with no special packaging or deployment descriptors
  • “web.xml” and “faces-config.xml” are optional in most of the common cases
  • Typesafe dependency injection is now part of the Java EE platform
  • Add @Path on a POJO allows you to publish it as a RESTful resource
  • EJBs can be used as backing beans for Facelets-driven JSF pages providing full MVC
  • Java EE 6 WARs are known to be kilobytes in size and deployed in milliseconds
  • Tons of other simplifications in the platform and application servers

Nota Bene: Spring Framework is not a standard – it is a product and an implementation of a framework. This means, there is no alternative vendor. Please, keep this always in mind.

Actually, it’s better to link to the original post instead of refactoring the information. There is no need to argue anymore.

Original Post here:



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s