I believe the one thing that the java.lang.reflect.Proxy won't do that
JBoss needs is to generate implementations of abstract classes (rather
than interfaces) this is important in a few places (EJB 2.0 CMP for one)
danch
Neale Swinnerton wrote:
> I've just submitted patch 517088 to completely remove the jboss proxy compiler
> and replace it with use of java.lang.reflect.Proxy.
>
> The BCEL looks pretty good for all sorts of stuff, but the JDK Proxy class
> does everything that the JBoss one does.
>
> An 'interesting' use of the BCEL would be to post process the .class files
> before deployment for production and completely remove the
>
> if (log.isDebugEnabled()) {
> ...
> }
>
> code from the .class file.
>
> I can't get too excited after the miniscule performance increase you'd get
> from this (I've followed the log4j discussions on this in the past on this
> list and others). but as an intellectual exercise it might be quite
> interesting to do...
>
>
> On Mon, Feb 11, 2002 at 08:35:44PM -0800, Jason Dillon wrote:
>
>>Any thoughts on replacing our proxy compiler with the Byte Code
>>Engineering Library, recently added to the list of Jakarta
>>sub-projects?
>>
>>--jason
>>
>>
>>_______________________________________________
>>Jboss-development mailing list
>>[EMAIL PROTECTED]
>>https://lists.sourceforge.net/lists/listinfo/jboss-development
>>
>>
>>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
