Lamia's stack and heap based memories...

Before I started reading about hibernate, I had a hard time which technology to learn first. ORM or Webservices? As they are both essential technologies, I am left with such confusion. I already read some introductory articles about webservices, mainly Apache SOAP/Axis. But there's just nothing to do with it now so I read about ORM too! But which ORM tool to use? I've already heard of two co-I.T. professionals who use Ibatis, another ORM tool. I was confused until I read about ORM in wikipedia and discovered that hibernate is indeed the widely-accepted, most matured, opensource ORM tool out there. As a starting point, I googled and found this article to be helpful...

http://www.gloegl.de/5.html 

I was fiddling witht the new Eclipse IDE 3.2 (nothing to do with this post). I was experimenting, creating my own version of the singleton ConnectionManager class that I got from my senior during my training with my previous company. I had a lot of doubts about inheritance in my mind, especially about member variables. Since member variables are logically not overidden(there'sno point of doing so according to experts), I wondered what would happen if I declared a member in an abstract class, and declare it again in base class. So I tried something like this:

class A

{

    protected int p;

    public int getP()

    {

        return p;

    }
 

}

class B extends A

{

    protected int p;

    public int getP()

    {

         return p;

    }
 

} 

Now this is absolutely legal, it will compile and will not make any runtime exception(I think). But I was told that this is a bad practice and could lead to hard-to-find bugs. If somebody needs an explanation, when an instance of class B is created and the getP() method is invoked the p that is returned is that of B's. Unless of course you call super.getP(). Plain ol polymorphism. The point in this post is that this is a bad practice and should be avoided at all cost.

Just as I was modifying our database, I thought again of support for localizing our app. I was given advise by someone here in the devpinoy.org community, to support localization in your app your app must be planned with it from the ground up. Since we don't have that much data yet, it won't hurt to change things in the database. I'm gonna be changing the fields that needs localization support to UTF-16 as suggested in this article in the mysql website.

http://mysql.com/doc/refman/5.0/en/mysql-config-wizard-character-set.html

After about 4 months of development, I was finally able to deploy our app. I had a lot of trouble dealing with Virtual hosting for Apache and Tomcat and had to fix a lot of JSP/Servlet/Struts related stuff... Finally, my apache server and tomcat server are now best friends. Me and my boss plans on developing a simple site and put this incomplete app as our first entry on our company portfolio. There are still a lot of tightening up to do like adding more features and tightening up security.

Check it out: http://www.gm-recruitment.com