I fixed the bug where field level annotations are swallowed (patch not applied
by the CGLIB team though)
http://sourceforge.net/tracker/index.php?func=detailaid=2796998group_id=56933atid=482368
But I could not fix the bug where generics information is simply swallowed (not
enough internal
that cglib with annotations issue only shows when using cglib to instrument the
domain class in compile time.
but I'd agree with drop it, actually i'm happy with that :D, cglib issues has
taken too much time from us
On May 12, 2010, at 4:10 PM, Emmanuel Bernard wrote:
I fixed the bug where
Seems it is a simple choice after all. Let's just drop it.
--Hardy
On Wed, 12 May 2010 10:41:38 +0200, Strong Liu st...@redhat.com wrote:
that cglib with annotations issue only shows when using cglib to
instrument the domain class in compile time.
but I'd agree with drop it, actually i'm
I think the time has come to drop CGLIB support :( It is just becoming
near impossible to get them to respond to issues. We even recently sent
them 2 patches of major issues and still cannot get them to apply the
changes upstream and cut releases.
So that leaves us the choice of deprecating
Is there any advantage of CGLIB over javassist?
On Tue, 11 May 2010 16:24:12 +0200, Steve Ebersole st...@hibernate.org
wrote:
I think the time has come to drop CGLIB support :( It is just becoming
near impossible to get them to respond to issues. We even recently sent
them 2 patches of
these are the issues Steve mentioned below:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4703
https://jira.jboss.org/jira/browse/JBPAPP-2971
to be fair, these issues can be workaround, and we already have patches, users
who run into these issues can pick up our patch for cglib
Afaik it simply a matter of what library you might already be using. nbsp;I
have heard it or javassist do one thing better or faster, but I have not seen
any evidence of that (nor have I tried to quantify).
-- Sent from my Palm Pre
st...@hibernate.org
http://hibernate.orgOn May 11, 2010 9:34
I thought one of the issues was that cglib does not handle annotations?
nbsp;That's a pretty big 'workaround' if that's the case.
-- Sent from my Palm Pre
st...@hibernate.org
http://hibernate.orgOn May 11, 2010 1:06 PM, Strong Liu
lt;st...@redhat.comgt; wrote:
these are the issues Steve
Since it is really ASM for which we are interested in isolation, I
guess we would take the cglib-nodep jar which 'bundles' ASM as
net.sf.cglib.asm (perhaps via jarjar as well) and run jarjar on that
to repackage net.sf.cglib - org.hibernate.cglib (or some-such). Is
that your understanding
Our (default) dependency on CGLIB is starting to cause problems due to
other libraries using newer versions of ASM (3.x) then the released
versions of CGLIB use (2.x). We have now been waiting about a year
for a new CGLIB release to use these newer ASM APIs. With 3.3 being
eminent, we
jarjar http://code.google.com/p/jarjar/ can be a good option when you're
looking to avoid version conflicts. Guice uses this to depend on a specific
version of cglib.
On Mon, May 19, 2008 at 1:29 PM, Steve Ebersole [EMAIL PROTECTED] wrote:
Our (default) dependency on CGLIB is starting to cause
11 matches
Mail list logo