Joshua Java

Feedback for Comparing JVM Web Frameworks

Posted on: November 16, 2007

I’ve written a feedback for Matt’s presentation since at the time being I’m also doing a research on several web framework.

Thing should be noted out:
Seam is tightly coupled with JSF. Matt wrote in the Seam point that JSF as one of the cons for Seam. Though he didn’t quite explained in detail regarding this point. I assume he meant Seam is tightly coupled with JSF. This is not true because since Seam 2.0, Seam has been loosely coupled with JSF.
Several work to integrate other web framework with Seam such as:

  1. Seam support for Wicket
  2. Seam integration with Wicket
  3. Integrate ZK with Seam

Seam works best on JBoss Application Server. Michael Yuan has a brief explanation regarding this.

Seam is Designed for EJB 3. Again that’s only relevant for Seam 1. Since Seam 2.0, Gavin already received alot of community feedback and learnt the lesson from Seam 1. Although at the beginning Seam is designed for EJB3, but Seam 2 works with POJO as well.

Will Tapestry be rewritten again for Tapestry 6? Why did Struts2 didn’t get the same comment? Struts2 is a major rewrite since Struts1.

Tapestry has no desire for backwards compatibility between releases. Again, why did Struts2 didn’t get the same comment. Struts2 is not backward compatible with Struts1 at all.


4 Responses to "Feedback for Comparing JVM Web Frameworks"

I actually think many people comment that Struts 2 is mainly called Struts because of marketing considerations. 🙂 Otoh, it does share the same model 2 heritage.

Personally, I am not horrified with massive API breaks, but it is very, very important that the framework does it’s best to assist you with updating in case you’d need it. We (Wicket) has gone through great lengths doing this by providing a migration document (see and by doing things like making overridable methods final for the time being so that your code will break hard. And the lack of a clear migration path is exactly what I’ve heard many people complain about when it comes to Tapestry. Also, if the versions are really that different (I don’t know tbh), you might wonder whether it wouldn’t be more appropriate to pick a new framework name. Indeed, that same comment goes for Struts 2.

My 2c

I’m willing to believe that my cons aren’t cons. However, I do believe that each framework has cons. Do you have any proposed cons for Tapestry and Seam?

About the Wicket Seam Integration: The correct link is because the link you posted above is pointing only to a part of the article.

Struts2 isn’t a rewritten version of Struts, Struts2 is WebWork, a completely different beast…

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s


Flickr Photos

%d bloggers like this: