Posts Tagged ‘Eclipse WTP’

WTP Bug 256185 – 180 Degrees

February 13, 2009

My miserable situation has turned around by 180 degrees . This morning I got a piece of advice from Valentin in the newsgroup. I downloaded the 3.1M5 version of WTP. My problem disappeared. Now I could launch the target platform successfully with the the code I’ve checked out from HEAD.

I inserted some System.out.println statements in a Java class. When I tried to reproduce the bug on the target platform instance, the output was displayed in the console window on the *development* platform, not the target platform. I wonder if this has to do with plug-in technology. Very interesting indeed! I’m looking foward to Mr. Mandel’s visit to our class as he’s going to speak about Eclipse plug-in architecture. (You know what, he put a comment in my blog this morning.)


WTP Bug 256185 – A Miserable Week

February 12, 2009

After writing two postings, I would like to share about my miserable week. As I’m 100% green with WTP, I encountered two problems that have nothing to do programming per se. It reminds me of doing a science  experiment when I was a high school student. I’m still trying to set up the apparatus properly before I can tinker with the Java code. The first problem has been resolved after inspecting the Java code in light of the error messages. The second problem has to do with launching the target WTP platform from the development platform (i.e. the Plug In). Here’s my log on what I have gone through.

After reading the stack trace attached to the Bug Report, I checked out the component org.eclipse.wst.wsdl.ui from the CVS reposistory. I got error messages from the compiler. I had followed all the steps in the tutorial. I decided to post up my problem as a comment to the Bug Report.

I followed the red dots and inspected the Java import statements. Some classes such as org.eclipse.wst.wsdl.WSDLElement were not found. So I created a new workspace and checked out two compontes, namely org.eclipse.wst.wsdl and org.eclipse.wst.wsdl.ui. I didn’t get any error messages this time. I was SO glad that the problem was resolved.

Following the stack trace attached to the Bug Report, I inserted one line of Java code,  System.out.println( “1. dropDown…” ), in Then I tried to run it with the target WTP platform. (I already used the target platform to reproduce the bug successfully.) For some strange reason, the WSDL Editor was not launched at all.

After a while, I decided to look up Eclipse newsgroups (that was suggested by David Williams who commented my blog some time ago). I used “WSDL editor” as a search word. I was very surprised to know that someone had a similar problem. I was even more surprised that the problem was raised by Jesse Valianes, a student at Seneca. I never met him on the campus.

I found out that Jesse’s problem was not the same as my problem. My target platform is 3.1M4 and I checked out the components from HEAD. I tried several times again to launch the target platform from the Plug In. It still failed. Finally I decided to post my problem to the newsgroup.

Before I went to bed, I found out that Valentin had replied to my inquiry in the newsgroup.

I followed his suggestions. But  I still had the same problem. So this afternoon I posted some screenshots to the newsgroup again. I’m now waiting… Right now, I feel a kind of stuck. I know I have to be patient for the time being.  Nevertheless, I do feel being supported by the newsgroup and Valentin.

How are the other fellows in our WTP class doing? Mmm…

Eclipse WTP – It’s Worth Going To Class

February 12, 2009

I can’t believe it. Our WTP class has entered the fifth week now. On Tuesday (Feb. 10) Jordan wanted to show us how to use the Eclipse debugger to fix a bug. He has found some very helpful video clips. I recommend these tutorials to everyone in our class, especially those who were absent that day.  Jatinder showed us how the book, Eclipse Web Tools Platform: Developing Java™ Web Applications, has helped him to navigate through the packages in order to locate the bug. Watching his live demo was just different from reading his blog.  I hope that all of us can share and discuss our experiences when we meet as a class in the near future.  As for myself,  I’ll see if I will acquire a litte more experience in fixing a bug before Angel Vera from IBM shows up in our class next Tuesday.

Eclipse Bug Day – A Glimpse of Hope

February 12, 2009

It’s been a miserable week for me. I will share about that in another posting. I just read our course Main Page a few minutes ago. I felt hopeful when I saw an announcement about Eclipse BUG Day. It seems that it’s going to be an international event. I don’t know what’s going to happen on that day. Right now I feel stuck in fixing the bug; yet I will persevere since the Eclipse Bug Day is coming. Jordan, thanks for posting it up.

Eclipse WTP – Bug 256185 Reproduced

February 4, 2009

Bugzilla – Bug 256185

Description: Null pointer when changing reference kind in the properties view with type combo box open in design view

Build ID: WTP 3.1

Steps To Reproduce:
1. Open PhoneBanking/PhoneBanking.wsdl
2. Go to design view, select BillInfo from the payBill operation

design view

3. Right click and show properties. Make sure the properties view shows the general information for the part associated with BillInfo

properties view

4. In the design view, open the combo box. While the combo box is expanded (i.e. the list of options are open), click on the radio button “Type” in the properties view for Reference Kind

the radio button

5. A null pointer exception will be thrown

the problem dialog box

Eclipse WTP – Bug# 256185 Reproduced with Community Support

February 4, 2009

I’m often curious about the NullPointerExceptions thrown by the JVM. After reading Dave Humphrey’s encouraging comment to my blog, I decided to take a look at Bug# 256185 today. Kevin and Jatinder have blogged their experiences in reproducing their Bugs. I would like to be able to do so soon.

I tried to follow step 1 in the Bug’s Report. I knew I had to find or download the example somewhere in the WTP target environment. I used the Help Contents feature, even using “examples” as the search word. After a while, I felt that I was at a dead end. Then I remembered Jordan’s advice: Cry for help! As the last resort, I looked up the Bug Report again and emailed the QA contact person. Then I walked away from my laptop for a while…

An hour later, I already got a reply from Valentin Baciu. His reply was brief but very helpful. He first congratulated me for working on some of the WTP bugs. Then he showed me to use the XML Example project wizard to create the example that I tried SO hard to find. Lastly he referred me to ask questions through the Bug Report in the future. He has assured me that they are “typically fairly responsive.” As a result, I used the “login” feature on the Bug Report to enter my first comment there. I also added my email address to the “cc” list. Now I recall what Dave and Jordan have said some time ago: “There’s a community out there to support you.”

Fixing Eclipse WTP Bugs – Complicated, Difficult, But Not Alone

February 3, 2009

Our open source development course has entered the fourth week. Eight fellow students have already posted the Bugs that they want to work on. I need to catch up. Hopefully I will post up a Bug within two or three days. Otherwise I will miss the thrill and frustration of fixing a bug.

Our class today began with Jordan’s demonstration on fixing a Bug. Surely the Eclipse debugger was handy. He cared a lot about us. At different points of time, he asked us if we understood all the steps that he did. All of us were appalled when Jordan got it fixed. This only lasted for a moment though. Soon he showed us that another bug was introduced…

Then Jordan asked the students about their impression of fixing bugs. One student said that it was complicated because one had to go through many folders and classes. Then you wrote a few lines of code in a Java method. Another student said that it was difficult because you had to find the location of the bug. I agree. The whole process is like looking for a needle in a haystack (or in an ocean).

Jordan has given us some practical advice:
1. You don’t have to understand everything. Probably no one does.
2. Focus on a small piece of code.
3. Do not try to work alone.
4. Cry for help when you reach an impasse.

How may we put this into practice? Keep on blogging our experiences (both positive and negative) and use Eclipse WTP newsgroups as commented by David Williams. (I couldn’t believe that an experienced WTP developer has read my blog and put a comment there.)  I’ve checked out the newsgroups. Pretty neat.

Finally, Jordan asked Jat to give a demo on what he has experienced in reproducing “his” Bug (#203257).  His demo has sparked off discussion among the students. As mentioned in his blog , he has discovered something else (another glitch) that is not behaving nicely. Jordan advised us to draw a distinction between fixing a bug and enhancing a feature. Yes, our goal here is fixing bugs.

Eclipse WTP Tutorial and Project Wiki

January 30, 2009

Jordan has posted many resourceful links on our course wiki page. After getting some emails from the students, he asked me to post a link to the WTP tutorial in my blog. No problem.

Actually I found Jordan’s link to Eclipse Community Education to be useful. From there I browsed the Project Wiki. It gives me a broad view of the   Eclipse WTP project. Interestingly I have found that there’s not much  for the category “How to… for WTP Developers.” As we gain experience in fixing bugs, I think some of the contents of our blogs could be proposed to the WTP community for public use.

Finally Jordan has posted some links to WTP-related resources under Week 3 and Week 4. It’s worth reading. The reading will prepare us to understand what our guest speakers are going to say in the coming two weeks.

Eclipse WTP – Reading Blogs & Fixing Bugs

January 30, 2009

As I was reading the blogs on Open Source @Seneca Planet, I noticed that a few fellows in our WTP class have posted their BLOGS about the BUGS. Reading their blogs has motivated me to undertake the challenge of fixing WTP-related bugs. Then I discovered that Kevin’s Blogrolls [1] has linked up all these blogs.

Let us continue BLOGGING our experiences in navigating our ways through the huge code base of WTP project as well as our failures in fixing the bugs. I have a hunch that all our blogs will enable us to build a knowledge repository for fixing WTP bugs. Hopefully some experienced developers in the Eclipse WTP newsgroup will comment on some of our blogs!

Indeed Dave Humphrey has blogged recently why he wanted his students at Seneca College to blog a lot… [2]

We Teach Who We Are

January 27, 2009

My colleague Jordan has graciously allowed me to sit in the open source development class(OSD600, DPS909) offered by the School of Computer Studies, Seneca College. After attending the Teaching Open Source seminar at FSOSS 2008, I have become interested in observing how students could interact with open-source communities such as Mozilla and Eclipse Web Tools Platform(WTP). I am also curious about how a professor could teach such as a non-traditional project-based course effectively. I have a hunch that there are many issues of teaching and learning that I could explore here.

On the first day of the class(Jan. 13), I was impressed by the remarks of my three colleagues. Dave Humphrey told the students in an inspiring way: “You are not ready to work on these big open-source projects such as Open Office and Eclipse Web Tools. You must persevere. In the end, you would show that you’re good developers.”

Fardad told the students in a straight-forward manner: “I do not know much about Open Office. We learn as we go.”

Jordan told the students in a humurous way: “Our goal here is to fix bugs in WTP.” A week later(January 20), Jordan was showing the HUGE code base of WTP to the students. He said, “I do not know much about this code base. When we want to fix a bug, we ASK HELP FROM THE COMMUNITY.”

I was amazed by my colleagues’ transparency. They were honest with the students: “The professors do not know everything!” This reminds me of what Parker Palmer has said in his book The Courage To Teach: “We teach who we are.” Maybe I have to be willing to reveal my limitations as a teacher if I want to teach such a course effectively. Rome is not built in a day. As for the students, have they learned to nurture a spirit of taking challenges and perseverance? The challenges become even greater since(I think) most of them are full-time students who have to work hard on other courses at the same time.