Joshua Java

Archive for the ‘Java’ Category

Currently I am making a website using Ruby on Rails for my beloved. Moving in from Java I found developing Rails apps is very convenient as I can see changes directly (with few exceptions though) without restarting the server. With that in mind, I was wondering whether we still need to unit test Rails apps. Luke Francl explained in his presentation and interview why testing is overrated. I must agree that it is quite true that unit testing seems to be overrated for Rails apps because unit testing grew up from static language like Java and because you want to make sure your code works before you test it on a real server. So back to the question, what’s the point of doing TDD and BDD in Rails apps? If I’m developing with Rails, what is the advantage of unit testing over usability testing by human? Is there still anything useful from doing TDD in Rails?

Advertisements

2009 is coming to your way and it’s time to get ready on what technology lies ahead. Refactor, refactor and refactor is the theme for 2009. A whole new technology is coming your way and it’s good to take a sneak peek on what technology is worth evaluating to be used for our projects in 2009. The first half technology are the technologies that you should keep your eyes at while the next half are the technologies that you might want to start trying for your next project in 2009. So here are the lists for 2009:
Read the rest of this entry »

On my previous Tapestry 5 article I mentioned how difficult it is to create a custom component with Struts 2 compared to Tapestry 5. Since in our legacy apps we used Struts 2 and I got a task that made me to create a custom component I might as well just document it here since it is not documented in Struts 2 documentation nor the Struts 2 book.
Read the rest of this entry »

At the time being I am doing a Flex project for my client. Alot of people has been praising Flex for being the answer in the RIA world. In one way and the other, it’s true: Flex is really sexy, because it can bring all of the interactiveness and statefulness from desktop app world to the webapp world. But there is a but. It’s good from user’s point of view. But from developer’s point of view, it’s a different story. You might have to think again whether or not to use Flex for your next project if you are currently considering to use Flex. What I’m saying here doesn’t mean that Flex is not good, but rather I’m saying there is a consideration you might have to think about before you want to use Flex and there is consequences to get all of those sexiness.

Flex is good for a reason, but it’s not for the other reason. Doing almost everything in Flex is quite different compared to regular web development using html, css and javascript (or web 2.0 as some people say). I’ve even made a presentation about this and shared it with JUG-Indonesia several months ago. For some people there will be some pains they have to go through when entering the Flex world. And for some people these differences might not be acceptable because in one way or the other it can affect the productivity of the developers in the team. Anyway, all in all the reason you might not want to use Flex is:
Read the rest of this entry »

Tags:

Yesterday we were evaluating GWT to be used as a wrapper for the GMap API. And one thing we need in our apps is to be able to drop marker and follow where the last marker is dropped.
Read the rest of this entry »

Tags:

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 »