Superclass property not visible when doing session.load()

bshaw · **Joined:** Mon Feb 23, 2004 5:11 pm **Posts:** 39

I am trying to upgrade from H2 to H3. I followed the migration guide. I am using the Classic Session (for now).

Consider the following (simplified) classes:

Code:

public class BaseEntity implements Serializable {
    private Long id;

    public final Long getId() {
        return id;
    }

    public final void setId(Long id) {
        this.id = id;
    }
}

public class Customer extends BaseEntity {
    private String name;

    public String getName() {
        return name;
    }
    public void setName(String n) {
        name = n;
    }
}

I inserted a Customer record into the database and I have the id. Now, in a new session, I do

session.load(Customer.class, (Long)tempid);

This actually loads the customer object and I could even print the name property. But when I do cust.getId() I get null. Very weired. I added the following method in the Customer class that simply invoked super.getId();

Code:

public Long getSuperId() {
       return super.getId()
}

Now, if I do cust.getSuperId(), i see the actual id. In short, I load the Customer object from the database, then
cust.getId() returns null, while
cust.getSuperId() returns the id.

I am completely lost. This issue is not just with the id property, it affects all the properties in the super class. This used to work just fine in H2. Any pointers?

bshaw · **Joined:** Mon Feb 23, 2004 5:11 pm **Posts:** 39

I thought may be this was happening due to the zillion jars I have in my application's class path. So I started with an empty class path and added the jars as required to run my simple test. Here is my class path.Please note the 3 jars in bold did not come shipped with H3. I had to add them myslef.

j2sdk1.4.2_03 libraries
my source folders
hibernate mapping file folders
hibernate2.jar
commons-collections-2.1.1.jar
commons-logging-1.0.4.jar
dom4j-1.5.2.jar
junit-3.8.1.jar
log4j-1.2.9.jar
common-beanutils.jar
classes12.jar (oracle driver)
cglib-full-2.0.2.jar
ehcache.jar
jta.jar
commons-lang-2.0.jar

I still see the problem.

bshaw · **Joined:** Mon Feb 23, 2004 5:11 pm **Posts:** 39

Minor typo in my previous posting its hibernate3.jar not hibernate2.har

emmanuel · **Posted:** Fri Mar 25, 2005 12:22 pm

Your class was not lazy="true" and it is now since this is the new default.
This is not an answer though.

bshaw · **Joined:** Mon Feb 23, 2004 5:11 pm **Posts:** 39

I removed the final keyword from the method signature and it worked!!!!!!. Obviously, something is not right (may be in the CGLIB). For now I am going to remove the final key word in all super class methods. But it will be nice if this could be fixed.

emmanuel · **Posted:** Sat Mar 26, 2005 5:22 pm

This is explained in the doc. A lazy class need not to be final nor have final properties. This is due to the very nature of proxying

max · **Posted:** Sun Mar 27, 2005 6:08 am

maybe we should error/throw on this situation ?