Concern over CGLIB's inactivity is certainly valid. However, our internal load-testing
of javassist (a few months back) revealed that the library's perf characteristics
aren't quite ready for prime time. In some cases, our system performed 2x faster with
cglib v. javassist. I don't recall the exact reason why, but possibly this was due to
excess synchronization in javassist code (I could be wrong about this though).
-nikita
-----Original Message-----
From: hibernate-dev-bounces(a)lists.jboss.org [mailto:hibernate-dev-bounces@lists.jboss.org]
On Behalf Of Chris Bredesen
Sent: Friday, May 29, 2009 7:30 AM
To: hibernate-dev(a)lists.jboss.org
Subject: Re: [hibernate-dev] Why cglib was replaced with javassist?
First result from a search in JIRA reveals this....
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2506
So I think that's your answer :)
-CB
Unmesh joshi wrote:
hi,
Till hibernate 3.2 cglib was default bytecode provider. why was it
changed to javassist?
thanks,
unmesh
------------------------------------------------------------------------
MSN Battles We pitch one stalwart against the other and give you the
power. Who will you vote for? Share photos while you chat with Windows
Live Messenger. <
http://battles.in.msn.com/>
------------------------------------------------------------------------
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev