I am trying to disable CBLIB by adding “hibernate.cglib.use_reflection_optimizer false” to my hibernate properties, but this doesn’t seam to work under hibernate V3.

I have also tried to add it to the system properties, but without success.

The only way I can prevent hibernate from generating CBLIB proxies classes is to add the Lazy=”false” property to each class.

Is this correct?

another option is to put default-lazy="false" in the hibernate-mapping element.

The reflection_optimizer is for cglib support for more efficient properties read/write operations....not related to lazy, so you need both to avoid this. (im not sure if i'm forgetting something so try it out ,)

Probably it is a good time to drop "reflection_optimizer" (or to dissable it by default), SUN JVM generates code since jdk 1.4.2 to optimize native calls in reflection itself, double code generation just wastes memory (cglib is bit faster, but difference is too trivial to be usefull for data access).

ok - could you put this info in the jra so it wont be lost ?

-max

Thanks for the replies.

But...

Does the hibernate property "hibernate.cglib.use_reflection_optimizer" work under V3?

IMHO she be broken!

yes it does. and no it is not broken since it does not have anything to do with lazy stuff.

-max

Sorry.

Docs are not very clear as to what this property affects.

Setting the "hibernate.cglib.use_reflection_optimizer" property to false does not seem to work with hibernate V3 (latest production release), it works with 2.1 though. I think the original poster has a valid issue here. Could the team please check? Thanks!

that options disables the usage of cglib while performing set and get operations - it has never completely disabled cglib.

cglib is activated when you have lazy/proxy classes which in H3 now is default for every class. If you dont want that then set lazy="false" on your classes.

Thanks, but I think it's not that easy. cglib seems to be activated also through other properties/conditions than just not setting lazy="false" (which prevented calling cglib optimization methods but it sometimes still decides to call some other cglib "BulkBean" methods). It seems to me kind of dangerous and unnecessary to walk the methods through reflection upon startup and I feel that it would be safer to have cglib disabled by default. Depending of the order of the methods and what classes you use inside, cglib easily gets trapped in recursive/looping patterns and will then throw out of memory errors or just stall. Your team mate mentioned that there's plans to abandon the use of cglib, are there any news on that? Thanks

you need to report such claims as bug reports with failing test cases.

cglib is used for proxying and that is enabled by default in H3 and as I told you to not have it do its thing you need to run with lazy="false" and/or default-lazy="false" to not have cglib invoked.

And if someone wants to replace cglib with something what should it be ? It would be something else that needed to proxy all the related classes and there is only a few ways to do that right (and as far as I know cglib does it fine ;)

He was talking about possibly not using cglib for reflection optimization. As Max mentioned, cglib usage will *not* be removed for the lazy/proxy stuff.