views:

188

answers:

3

I have an instance of a class that I got from a Hibernate session. That session is long gone. Now, I'm calling toString() and I'm getting the expected LazyInitializationException: could not initialize proxy - no Session since I'm trying to access a reference which Hibernate didn't resolve during loading of the instance (lazy loading).

I don't really want to make the loading eager since it would change the query from about 120 characters to over 4KB (with eight joins). And I don't have to: All I want to display in toString() is the ID of the referenced object; i.e. something that Hibernate needs to know at this point in time (or it couldn't do the lazy loading).

So my question: How do you handle this case? Never try to use references in toString()? Or do you call toString() in the loading code just in case? Or is there some utility function in Hibernate which will return something useful when I pass it a reference which might be lazy? Or do you avoid references in toString() altogether?

A: 

If all you want to return is the ID of the object, I imagine calling getID(), then parse the int/long as a String value at the moment you want it displayed would work just fine. At least that's how it seems based on the question.

EDIT

http://stackoverflow.com/questions/578433/how-to-solve-lazy-initialization-exception-using-jpa-and-hibernate-as-provider

After viewing the comment and doing some searching I believe this may be most beneficial to your scenario.

Woot4Moo
That will throw the LazyInitializationException because the reference hasn't been resolved, yet.
Aaron Digulla
Aaron, after reading this comment I edited my post. Please see the new information and let me know if this resolves the issue.
Woot4Moo
@Woot - The answers won't help. The lazy initialized values will never be read. The tx is committed. The connection closed.
Thomas Jung
Yes I see that the transaction is already committed. However, in the post it is a possibility to refactor the existing code to use the OpenSessionInView pattern found here: http://www.hibernate.org/43.htmlIf that is not doable in Aaron's environment than so be it.
Woot4Moo
@Woot: I have to agree with Thomas.
Aaron Digulla
At the time I call toString(), I have no session and I don't want to create one. The question is really: How can I make toString() work inside and outside of a session?
Aaron Digulla
+1  A: 

I've found a workaround:

public static String getId (DBObject dbo)
{
    if (dbo == null)
        return "null";

    if (dbo instanceof HibernateProxy)
    {
        HibernateProxy proxy = (HibernateProxy)dbo;
        LazyInitializer li = proxy.getHibernateLazyInitializer();
        return li.getIdentifier ().toString ();
    }

    try
    {
        return Long.toString (dbo.id ());
    }
    catch (RuntimeException e)
    {
        return "???";
    }
}

So what this code does is it fetches the ID (a 64bit number) from the object. DBObject is an interface which defines long id(). If the object is a Hibernate proxy, then I talk to its LazyInitializer to get the ID. Otherwise, I call id(). Usage:

class Parent {
    DBObject child;
    public String toString () {
        return "Parent (id=..., child=" + getId(child)+")");
    }
}
Aaron Digulla
+2  A: 

It's possible to do this by setting the accesstype of the ID field to "property". like:

@Entity
public class Foo {
    // the id field is set to be property accessed
    @Id @GeneratedValue @AccessType("property")
    private long id;
    // other fields can use the field access type
    @Column private String stuff;
    public long getId() { return id; }
    public void setId(long id) { this.id = id; }
    String getStuff() { return stuff; }
    // NOTE: we don't need a setStuff method
}

It's explained here. This way the id field is allways populated when a proxy is created.

EJB
+1 I like it; there is just a minor catch: I'm using DSL syntax, so my getter is called "id()", not "getId()". I guess I could add a second getter for this special case but maybe it's possible to tell Hibernate the name of the getter?
Aaron Digulla
Well, it's possible by creating your own implementation of org.hibernate.property.PropertyAccessor, and declare the fully qualified name as the value for @AccessType. On the other hand, you could create the setter (you'll need that too) and getter and make them private, so you won't see them from the rest of your app.
EJB