The reason is I don't want inconsistent defaults for bytecode generation. If this is handled by the integration layers that is fine, but let's get those layers configured correctly to use javassist by default.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Steve Ebersole > Sent: Thursday, April 13, 2006 12:06 PM > To: jboss-development@lists.sourceforge.net > Subject: RE: [JBoss-dev] Should 4.0.4 have cgilib in > jbossall-client.jar > > I would guess that actually breaks regardless as the thing > that gets serialized in the two cases is completely different > under the covers between those two versions of hibernate > because of the introduction of the javassist capability. If > this situation is really a requirement, we will probably need > to add some serious deserialization logic to the serializable-proxy. > > As for needing a version of hibernate where javassist is the > default bytecode library, I don't get why. For the > hibernate-int code we could handle that specifically in the > MBean. For the EJB3 case, we should be able to do something > similar. I am very against changing this default in Hibernate itself. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
