Hibernate Lazy Loading Proxy Incompatible with Other Frameworks

Question

I've come across several instances where frameworks that take POJOs to do some work crap-out with proxied hibernate beans.

For example if I xml annotate a bean for framework X and pass it to framework X it doesn't recognise the bean because it is passed the proxied object - which has no annotations for framework X.

Is there a common solution to this? I'd prefer not to define the bean as eager loaded, or turn of lazy-loading anywhere in the application.

Bozho · Accepted Answer · 2010-06-02 16:43:41Z

6

You can unproxy the object before passing it around:

public static <T> T initializeAndUnproxy(T var) {
    if (var == null) {
        throw new IllegalArgumentException("passed argument is null");
    }

    Hibernate.initialize(var);
    if (var instanceof HibernateProxy) {
        var = (T) ((HibernateProxy) var).getHibernateLazyInitializer()
                .getImplementation();
    }
    return var;
}

answered Jun 2, 2010 at 16:43

Bozho

599k147 gold badges1.1k silver badges1.2k bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

bowsie Over a year ago

Thanks. I guess the best solution is to slot this code into an interceptor before any framework gets it.

Collectives™ on Stack Overflow

Hibernate Lazy Loading Proxy Incompatible with Other Frameworks

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related