Java EE or Spring Framework – Rule #1

July 3, 2013

Java EE

I came across a Java EE / Spring Framework post on DZone the other day.

It wasn’t the first, and it won’t be the last.

I want to get in the ring, but first we need some rules.

Rule #1 – Use of the Term “J2EE”

“J2EE” can only be used to refer to the J2EE 1.4 specification released in 2003.

“J2EE” can not be used in place of Java EE.

The current comparison is Java EE 6 to Spring Framework 3 (3.2.3).

Feel free to suggest a rule via comments or Twitter (@jboss_tm).


Sony PlayStation or Microsoft Xbox?

Microsoft Xbox. I can not imagine a life without Master Chief (link).

About Shane K Johnson

Technical Marketing Manager, Red Hat Inc.

View all posts by Shane K Johnson

2 Comments on “Java EE or Spring Framework – Rule #1”

  1. S. Wille Says:

    I didn’t get a reason to stick with spring mvc just for DI stuff. Maybe there are some cool things about spring webflow (are they?) but for new projects there is no reason for spring mvc over JEE to me. However spring hateoas looks pretty interesting.

    Reply

    • Frisian Says:

      Spring MVC is IMHO the most elaborate page-oriented Java web framework there is. Especially recommended, when you have to deliver more than plain HTML. Integrating Flying Saucer to create PDF from plain JSPs was a snap.
      Spring Webflow on the other hand works great with JSF, Facelets and RichFaces. From what I’ve seen, it’s the most boilerplate-free way of doing component-oriented web development. Facelets allow you to create reusable UI components, while Webflow allows you to create reusable, “componentized” workflows.
      Example: Let’s say, you have a dedicated search-popup for looking up people in your company. The UI is defined as a Facelets component with the JSF and RichFaces markup. The workflow inside the popup and the parameters passed to and from the popup are defined as a Webflow workflow.
      Now all you have to do in order to use it, is to have a button in the calling page and a corresponding action in the page’s workflow invoking the sub-workflow for the popup.
      Webflow is even able to keep track of nested popups.

      Reply

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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

%d bloggers like this: