Comments on: Why I will use Java EE (JEE, and not J2EE) instead of Spring in new Enterprise Java Projects in 2012

By: 5-10 kg abnehmen

5-10 kg abnehmen — Sat, 18 May 2013 23:20:03 +0000

It does appear, however, that hypnosis can help a person achieve his or
her weight loss goals. Cucumber contains sterols which
can help to lower cholesterol and prevent carbohydrates
from converting to body fat. Many people don’t have the time to weight themselves every day, but checking the scale on a regular basis can definitely help when you’re working to lose weight
and keep it off.

By: Sanjar

Sanjar — Thu, 28 Mar 2013 20:23:42 +0000

Nice article.
Jo, may I humbly throw in my 5 cents: migrate to JSF2, have a look at Seam3 (www.seamframework.org) and than at Apache Deltaspike – which is a synergy of Seam3+CODI MyFaces+Spring.
As JSF2 already in the market have a look at RichFaces, IceFaces and my favorite Primefaces (www.primefaces.org).

For the bookmarking, enjoy the ocpsofts prettyfaces.
We still use struts2, but agressively moving on a “it just works” tool-chain: Seam3 (CDI, etc.) + Primefaces (JSF2) – and enjoying it greately!

No more struts2 and JSF1.x!

By: Jo

Jo — Wed, 27 Mar 2013 13:46:04 +0000

Thanks Kai… appreciate your feedback..

By: Kai Wähner

Kai Wähner — Wed, 27 Mar 2013 06:32:12 +0000

Jo,
first, I think every web framework has advantages and disadvantages. However, I think the problems you are talking about are old issues.
Definitely, my answer is yes, I recommend JSF 2.x! There are many other great web frameworks available on the Java platform. However, if your team has experience with J2EE / JSF 1.2, then I would not think about using another framework. Getting started is much easier, and (as JSF 1.2 user), you will love JSF 2.0…
By the way, JSF (and Spring MVC) are a very good fit for (public) ecommerce web applications, compared to GWT, Vaadin, etc., because you have full (and easy) control over your presentation layer. The latter are great for internal applications where you want quick results, but in your case I think JSF 2.x is perfect.

By: Jo

Jo — Tue, 26 Mar 2013 21:19:02 +0000

Kai,
Would you reccomend Java EE (including JSF) for a medium to large ecommerce application… I hear issues with JSF (page bookmarking, large memory footprint with sessions due to state keeping etc).. however not sure these are all old issues already addressed in JSF 2.0/Java EE… .
Our team is mostly experienced in small to medium internal applications on JSF1.2/J2EE stack… trying to decide which would be better option for us Spring or Java EE in the long run…since majority of our new project is going to be work effort on the presentation layer, presentation framework is a key concern (JSF vs Spring MVC )… thoughts?

By: Kai Wähner

Kai Wähner — Tue, 12 Feb 2013 12:35:25 +0000

Well, the article is just one year and three months old My opinion did not change. I still think that you can solve most problems with Spring or Java EE. However, I still recommend Java EE in most use cases…

By: xxonnn

xxonnn — Mon, 11 Feb 2013 16:07:38 +0000

Hi Kai,
This article post on 3 years ago , what your opinion now Kai ? Are you still love your decision ?

By: Kai Wähner

Kai Wähner — Tue, 05 Feb 2013 07:38:45 +0000

Hi Chandra,

thank you. I think there is no subscription available (I have to check this out in the future. Probably, WordPress offers this functionality). In the meantime you can follow me on Twitter or connect via LinkedIn or Xing to see new blog posts.

Kai

By: Chandra

Chandra — Tue, 05 Feb 2013 00:08:36 +0000

Hello Kai,

This blog really helped me in clearing the confusion about Spring framework. Thank you very much.

By the way, How can I follow your blog posts, is there any subscription required?

Thanks,
Chandra.

By: juujuu - file sizes do matter

juujuu - file sizes do matter — Sat, 02 Feb 2013 13:31:18 +0000

But filesizes do matter – the are a rough measurement of the thickness of your stack – but not an absolute measurement.

Absolute measurement can easily be made by creating an invalid access against your favorite db layer tool. You’ll propably get about 100 – 200 levels of “stack” to your exception. Each level representing actual functional code your application has gone tru, before running into your exceptional code.

So, thickness matters.