Hi everybody,

I like to store the hibernate.properties in the same place as my other application configuration (xml files with mappings, pageflows, localization and so on in a central config directory) and therefore at app startup I use the setProperties() method of the Configuration class of 2.x (I use Version 2.1b4).

So far so good, but after a view test I think hibernate ignores at minimum one property setting if used this way. The property is



The effect is as follows. If I place the properties file in the classpath hibernate finds and use it (inclusive the reflection_optimizer property!) after the call of



and all works fine. If I store hibernate.properties in my config directory and run the following code



Hibernate writes to my log (after the first line) "hibernate.properties not found". After that I see while I debug it, that the properties are there and correct. In my case the reflection_optimizier is set to false, BUT




returns TRUE!!

This seems to me like a bug, am I right ?

THX for infos in advance.

Klaus

you have a '=' between hibernate.cglib.use_reflection_optimizer and false right?

No I haven't. Its exactly as I posted it. The properties are correct loaded in the myProp object and set to the Configuration object. But it doesn't change the reflection_optimizer value in the Environment.

Would say this is a bug since ENABLE_REFLECTION_OPTIMIZER is Environment Level and not Settings level. But there might be a reason I can't find.

hibernate.cglib.use_reflection_optimizer is a system level property, as per the documentation.

Missed that line until now. It is not a bug, it's a feature ;-)

A mis-feature actually, but one thats stupidly difficult to fix.

Thanks for the info. I will put my properties file back to the classpath.

By the way in my opinion it would be better to disable the reflection optimizer per default, because of the problem / restriction with the private setter/getter methods. I find for new users it would make the usage of hibernate easier, because if you follow the docs and best practices you would declare methods like setId(...) for example as private and then at application startup get the IllegalArgumentException caused by ReflectHelper.getMetaClass or exactly CGLIB as I wrote in another thread here.

The migration for hibernate 1.2.x users, which doesn't know CGLIB - as I - would be easier with this change, too. Not that I think the migration was difficult - beside this problem I have had no trouble and it was much easier than expected and works fine as before.

Therefore I think it would be better to disable the optimizer per default or if this is not possible / wanted to add a hint to the point 3.1.1 of the docs
(http://www.hibernate.org/hib_docs/refer ... classes-s1).

What do you think about that ?

But the reflection optimizer automatically disables itself if the exception occurs. That exception is completely nonfatal.