Hi,

after I switched our WebApp from Hibernate 1.2.3, which works really nice (THX for this cool solutions - helps us a lot. We use Hibernate since Version 0.9), to Hibernate 2.1beta4 I have a minor Problem.

At the start of the WebApp after Hibernate has compiled the mappings and begins to build the SessionFactory instance I get on most of my mapped classes the following exception message:

net.sf.hibernate.util.ReflectHelper getMetaClass
reflection optimizer disabled for: Foo, IllegalArgumentException: getXX
or in other cases setXX.

First of all my classes work fine with 1.2.3, the classes have nothing really special. All getter/setter pairs are existing. The names and mappings are correct.

The once on which Hibernate 2.1b4 throws the exceptions are these which I declared as private, like setId or set/getVersion (for optimistic locking). Normally Hibernate has no problems with this, but when I change them back to public and try it again every thing works fine.

I'm sure, that this couldn't be, but I have no idea what I made wrong and have nothing related found in the docs, FAQ or Forum search. Can anyone give me a hint whats going wrong ?

THX in advance

Klaus

This is not a problem for Hibernate it will work fine, just a little bit slower.

Cglib MetaClass.setPropertyValues can't be used on private setters

Ok, thanks for the info. I expected something like this, but was not sure.

Do you know if this is a temporary problem and a future version of CGLIB will do it or is it impossible ?

Klaus

It is possible to implement "fast reflection" for private members, but it needs to transform class (custom classloader, build tool or JVM debugging interface). Runtime implementation is more transaparent, but it is more limited too.
BTW reflection performance is not a very big problem, if you can use SUNs 1.4.2 JVM, you can ignore this optimization for most use cases.

Ok good to know, thanks.

I update when ever possible to the latest JVM and use the 1.4.2 from SUN - only one production server of a customer needs to be updated, but thats no problem.

And until know we have had no real performance problems - and I use reflection intensively in my application, too. Thats the reason why I was surprised that I get this problem with the private setters, because my reflection code access it, too. But now it is clear.

Even if we have no real performance problems I like to try every new feature of hibernate to get even more performance - because as you know an application can never be fast enough ;-)).

Thanks for your infos.

Would be pointless to optimize a so tiny time consuming stuff relating to JDBC queries.