Solving Eclipse Galileo problem in Karmic Koala (Ubuntu 9.10)

Yesterday i’ve upgraded my ubuntu with latest version 9.10 (Karmic Koala). After installing a lot of application, i was trying to install my favorite IDE, Eclipse 3.5 (Galileo). but something goes wrong after. i was not able to push OK button or Cancel button etc.
At that time i tought that main problem is my eclipse. Before i upgraded to karmic. i was install some plugins. that doesn’t matter in 9.04. but after install fresh copier of Galileo i still found this problem. Finally i found it, the main problem is about in how eclipse use GTK. In linux eclipse use GTK Library for handling interface, so it can be more native look. from what i was read here

Starting from 2.18 on, GTK+ changed some of its internal behaviour (google for “client side windows”). This change is intentional, and needed for other development. It doesn’t make any difference to programs using GTK+ correctly, but it makes problems with programs that use GTK+ in weird ways, making wrong assumptions that only accidentally worked in the past. So, to ease the transition until those programs get fixed, an environment variable has been introduced to simulate the old behaviour.

So it’s really up to the eclipse guys to fix their code, and to make sure they set this variable as a workaround until then in their own distribution. Ubuntu doesn’t have any influence on that.

And now for solving this problem is quite simple, you just enter this command in terminal before execute eclipse,

export GDK_NATIVE_WINDOWS=true

This solution is working in my box, if you don’t wanna execute this command in every launcing eclipse, you can add this line into .bashrc line, so whenever you launch terminal, it will automatically executed. Now i can enjoy working with cute koala.

Happy Coding

Simple Maven2, Spring 2.5, JPA and Hibernate integration

A few months ago, i’ve read a tutorial about spring 2.5 writen by Endy Muhardin (one of JUG Indonesia Hall Of Fame), that tutorial explained bout newest features of Spring 2.5, this version now supports Annotation. Configuration is no longer always in xml file. this made our effort to build program pragmatically  more easier to configure, faster and efficient.

But due to my bustle, and a regulation in place i work now. i have to leave Spring Frameworks. My project prefer choosing EJB3 and Struts2 as main developtment stack. the main reason is our client need a distributable application (even i know that spring support those too). Besides, developt a  ORM for handling database using JPA is more interesting for me than other approach. One question is, how bout people who doesnt need EJB feature which needed heavy container like Glassfish or JBOSS to running their application?.

Fortunately, Spring support JPA for connecting  to database, we can choose Hibernate or Toplink for JPA implementations. and it’s still can run in light web server like tomcat or jetty.  i’ll give you very simple example using JPA+Hibernate in Spring 2.5.