Joshua Java

Posts Tagged ‘web framework

Okay, so here’s the problem what I faced recently. I’m doing a research on using GWT because we’re currently evaluating whether or not to use GWT in the future. I am trying to use GWT and stuck on using the Hyperlink widget. There were two problems that I faced:

  1. First I need to figure out how does Hyperlink changed the content of our view. Well in traditional web framework, you just fire out the page file with the href attribute. This is not the case with GWT. Because everything is done in Asynchronous way. Gee weez I always had problem thinking in Asynchronous way of thinking.
  2. Okay, when I have solved that, I came into the next problem. When user clicked the link and user hit the back button it should redirect me to the previous content. Remember when I said that with GWT you don’t actually fire out the file name?

Now you must be saying: “Yeach mate, there’s already an example in the GWT’s Showcase example complete with the source code.” Okay you’re right, but the problem is, the code is too complex, there’s already custom code in it which makes it really difficult to understand the niche of GWT itself. “But mate, there are already numerous blog entry that wrote about this”. Well all of them only writes on how to display the historyToken, but this is not what we’ll do in real application.
Read the rest of this entry »


It has been a long time since Struts first showed up and filled in the Java web framework space. Many people nowadays are still using Struts which mainly because of legacy and investments reasons. But more people are moving away towards component based frameworks these days. JSF has got to be the most popular component framework out there, considering it is supported by many vendors and being itself as a standard from JCP. I’m not going to talk about JSF nor the up and coming release of JSF 2.0, instead I’m going to write about the other two popular component based web framework fostered by Apache: Wicket and Tapestry 5

In the near future there will be two interesting component framework that will be released by Apache Foundation: Wicket 1.4 and Tapestry 5 which I will elaborate in a very short few moment. Alot of people out there are asking, which one is better out of these two? First of all, we need to be on the same platform before continuing any further. This blog entry is not intended to be a web framework bashing discussion, but just to give insights for people who are curious about the difference between these two frameworks. The features that I will discuss will only be limited to the usage of the two frameworks.

Read the rest of this entry »

Tapestry 5.0.14 has been out recently and the Tapestry community is very excited with this news because Tapestry 5 is only one step away for being GA. In case you haven’t heard of T5, it’s an opensource component based web framework which is a total revamp from the previous version. Some people may not like the previous version because of the learning curve on using it. Some people even wrote rants about the previous version. But T5 is totally a different architecture with the same way of thinking as the previous version. So what’s so good about T5? And why should you consider it for your next project? Here’s my personal reason based on my experience building my opensource project using T5.
Read the rest of this entry »

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.

Matt Raible has written a blog entry on choosing web framework by categorizing it into types of application. He wrote 3 category:

  1. Consumer-facing, high-traffic, stateless applications
  2. Internal, more desktop-like applications that are stateful
  3. Media-rich applications that require a RIA framework like Flex

With these web-framework that falls on each category:

  1. Struts 2, Spring MVC, Stripes
  2. JSF, Tapestry, Wicket
  3. GWT, Flex, OpenLaszlo

I agree with him but with minor disagreement with the third category. Because really web 2.0 should be rich whether it is stateless nor stateful. We can add these richness to the webapps by applying AJAX and add CSS to it. Read the rest of this entry »