(Point taken, Sam.)
Hi, bcel-dev'ers! Any commentary on the two points below? The jar size issue isn't as important as the fact that I had classloader issues using Repository.lookup(className).... --Glen > -----Original Message----- > From: Sam Ruby [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 19, 2002 3:42 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Heads-up / opinions? - BCEL -> tt-bytecode > > > Comments? > > Glen - a pet peeve of mine is Apache projects who don't talk to one > another.... Grrr. > > - Sam Ruby > ---------------------- Forwarded by Sam Ruby/Raleigh/IBM on 02/19/2002 > 03:40 PM --------------------------- > > Glen Daniels <[EMAIL PROTECTED]> on 02/18/2002 06:50:07 PM > > Please respond to [EMAIL PROTECTED] > > To: "Axis-Dev (E-mail)" <[EMAIL PROTECTED]> > cc: > Subject: Heads-up / opinions? - BCEL -> tt-bytecode > > > > > Hi all. > > So, while looking into some reported problems with BCEL, I ran into a > couple of difficulties with the library. In particular, > there is no way to > get BCEL to make you a JavaClass from a java.lang.Class, so > it tries to > load the class, which was failing to work with JWS files on my home > machine. > > As an alternative, I switched over the code to use the > tt-bytecode library > from SourceForge (http://tt-bytecode.sf.net/), which has the following > benefits: > > 1) The jar is much smaller (128k vs. 335k) > > 2) It has an easy to use API for creating a new BClass with a Class > parameter, solving the classloader issue > > This is a BSD style license jar file. > > I'm going to commit my changes, which also make sure that JWS > files are > compiled in debug mode (at least for javac), and leave the > bcel.jar there > for now as well. If everyone's good with this switchover > tomorrow, I'll > remove bcel, if not I can roll back the change. > > --Glen > > > >
