The JavapUtils code is ugly. (I know because I added it.) If BCEL
provides a better way to get at the debug information then we should use
BCEL.
A big +1 from me.
Glen, please make sure the code continues to work with methods that have
array parameters and return values.
Thanks!
Rich Scheuer
+1
--
Tom Jordahl
-Original Message-
From: Glen Daniels [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 4:34 PM
To: 'Axis-Dev (E-mail)'
Subject: BCEL
I just revamped JavapUtils to stop using javap and start using BCEL
(http://jakarta.apache.org/bcel). The main benefits
The only objection I have you already brought up, relying on yet another
jar file. I'll whine about it, but I won't whine too loudly. Go ahead.
Russell Butek
[EMAIL PROTECTED]
Glen Daniels <[EMAIL PROTECTED]> on 02/14/2002 03:34:19 PM
Please respond to [EMAIL PROTECTED]
To: "'Axis-Dev (E-
+1. Even Xalan-J already uses this.
Thanks,
dims
--- Glen Daniels <[EMAIL PROTECTED]> wrote:
>
> I just revamped JavapUtils to stop using javap and start using BCEL
> (http://jakarta.apache.org/bcel). The main benefits of this are speed and resource
>conservation
> (we no longer have to spawn