Hi,

Why doesn't Hibernate automate proxy casting to avoid having to do this manually as described here? http://www.hibernate.org/hib_docs/v3/re ... ng-proxies

You can quite easily scan the bytecode for a casting operation and replace it with a Hibernate-safe call. For example:

Given:

(TargetType) myObject

replace it with:

(TargetType) Hibernate.getProxiedObject(myObject)

then define Hibernate.getProxiedObject() as:



Is there any reason we aren't already doing this? The benefit would be that you wouldn't need to introduce any Hibernate-specific calls in the code.

we dont rely on build time instrumention of *all* your classes.

I am primarily concerned with casting that occurs within the objects that Hibernate persists. If Hibernate were to fix the casting within those classes, it would be a huge step forward.

Also, I believe in the above case you could do the bytecode manipulation at runtime (as opposed to build time), the same time you are building the proxy classes. What do you think?

no we can't as we do cannot guarantee control over the classloader

Hi,

would it be possible to have another ant task which do that?
Just like there is the instrument task which do lazy loading, I think Hibernate could add another one. This would allow people which want this behavior to do it at compile time.

Or better (at least from my point of view), Hibernate could have an option to use lazy loading with bytecode instrumentation and return plain objects instead of proxies.

At my company usage, when we access a proxy, in 99% of time, we want to access other fields of proxy, so, we end up loading the object anyway. So, if we could use hibernate to just objects under demand (which is possible currentlywithout proxies and with bytecode instrumentation) and return plain objects and not proxies (which I don't know how to do it now) would be very good!

Thanks in advance.