The project is working fine now. Today, it took me 6 hours to fix only 2 bugs. The first one was the one that make the computer froze. The reason is that I forgot to implements the "IsSeriable" class in my Java Bean object. However, the debugger in GWT didn't prompt any errors. It just froze.
The second bug was the FlexTable widget. I tried to delete rows in the flex table using the method removeRow(int index). However, the GWT debugger kept giving "uncaught exception". I checked everything and all the logic was right. Finally, I gave up and got some rest and decided to do it tomorrow. However, I kept thinking about about it while lying on my bed. So I decided to give it some more time. I searched in GWT discussion group and found out that a lot of people got the same problem. Most of them though it was a bug in GWT flextable and tried to overwrite some method in the library. However, one person brought up an idea that FlexTable is the java.util.Vector, rows must be deleted from the last row. But the method removeRow(int index) says that index is the index of the row to be deleted. That confused a lot of people. GWT should get rid of the parameter and make it the default to delete from the last row.
At this point, I thought GWT is not a stable framework. It doesn't have good API and its debugger doesn't not give useful messages.
No comments:
Post a Comment