Menu
▾
▴
springframework-developer
|
From: Rod J. <rod...@in...> - 2003-11-15 17:21:12
|
Ted Neward is mentioning Spring in a conference presentation... http://www.nofluffjuststuff.com/2003-08-detroit/local/agenda.pdf I think it's significant that the word seems to have spread beyond the Spring team now sufficiently for others to raise it in public. |
|
From: Colin S. <col...@ex...> - 2003-11-16 15:38:27
|
You may not know this, but ASM has switched from an LGPL to BSD license. Given that BCEL is so big and bloated (BCEL is 20 times larger, 500k vs 25k), and runs a lot slower to boot, is it really worth using BCEL in any fashion any longer? Hibernate runs a lot faster with cglib-asm than cglib with BCEL. I think cglib 2 won't even offer the option of using BCEL... The only direct dependency we seem to have on BCEL right now is BcelAttributes and BcelAttributeWriter. What does everybody think? |
|
From: Rod J. <rod...@in...> - 2003-11-16 17:32:33
|
I vote to get rid of BCEL. Regards, Rod ----- Original Message ----- From: "Colin Sampaleanu" <col...@ex...> To: <spr...@li...> Sent: Sunday, November 16, 2003 3:38 PM Subject: [Springframework-developer] Is it worth keeping BCEL around at all? > You may not know this, but ASM has switched from an LGPL to BSD license. > Given that BCEL is so big and bloated (BCEL is 20 times larger, 500k vs > 25k), and runs a lot slower to boot, is it really worth using BCEL in > any fashion any longer? > > Hibernate runs a lot faster with cglib-asm than cglib with BCEL. I think > cglib 2 won't even offer the option of using BCEL... > > The only direct dependency we seem to have on BCEL right now is > BcelAttributes and BcelAttributeWriter. > > What does everybody think? > > > > > > ------------------------------------------------------- > This SF. Net email is sponsored by: GoToMyPC > GoToMyPC is the fast, easy and secure way to access your computer from > any Web browser or wireless device. Click here to Try it Free! > https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Mark P. <Mar...@Co...> - 2003-11-16 18:07:56
|
Hi, I vote to get rid of BCEL as well. It always seemed large to me. The ASM api indicates it supports attribute manipulation in the bytecode so I should be able to port the bcel package to asm. This feature bytecode libraries might not be that important anyway since the default storage mechanism for attributes will likely switch to side files instead of putting it in the bytecode. Mark > I vote to get rid of BCEL. > > Regards, > Rod > > ----- Original Message ----- > From: "Colin Sampaleanu" <col...@ex...> > To: <spr...@li...> > Sent: Sunday, November 16, 2003 3:38 PM > Subject: [Springframework-developer] Is it worth keeping BCEL around at > all? > > >> You may not know this, but ASM has switched from an LGPL to BSD license. >> Given that BCEL is so big and bloated (BCEL is 20 times larger, 500k vs >> 25k), and runs a lot slower to boot, is it really worth using BCEL in >> any fashion any longer? >> >> Hibernate runs a lot faster with cglib-asm than cglib with BCEL. I think >> cglib 2 won't even offer the option of using BCEL... >> >> The only direct dependency we seem to have on BCEL right now is >> BcelAttributes and BcelAttributeWriter. >> >> What does everybody think? >> >> >> >> >> >> ------------------------------------------------------- >> This SF. Net email is sponsored by: GoToMyPC >> GoToMyPC is the fast, easy and secure way to access your computer from >> any Web browser or wireless device. Click here to Try it Free! >> https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> > > > > > ------------------------------------------------------- > This SF. Net email is sponsored by: GoToMyPC > GoToMyPC is the fast, easy and secure way to access your computer from > any Web browser or wireless device. Click here to Try it Free! > https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Alef A. \(JTeam\) <al...@jt...> - 2003-11-16 18:19:04
|
+1 Just get rid of if, What Mark is saying about the side file approach indeed sounds like the best approach... Alef > Hi, > > I vote to get rid of BCEL as well. It always seemed large to > me. The ASM api indicates it supports attribute manipulation > in the bytecode so I > should be able to port the bcel package to asm. This > feature bytecode > libraries might not be that important anyway since the > default storage mechanism for attributes will likely switch > to side files instead of putting it in the bytecode. > > Mark |
|
From: Chris N. <ch...@si...> - 2003-11-16 18:33:54
|
Mark Pollack wrote: > I vote to get rid of BCEL as well. It always seemed large to me. The ASM > api indicates it supports attribute manipulation in the bytecode so I > should be able to port the bcel package to asm. This feature bytecode > libraries might not be that important anyway since the default storage > mechanism for attributes will likely switch to side files instead of > putting it in the bytecode. Yes, the new ASM 1.4 supports attribute reading and writing. CGLIB2 will use ASM 1.4 (or higher) so you won't even need an extra jar. FWIW, now that the JSR-175 spec is public it would be technically possible to read and write class attributes in a compatible format, which would allow you to seamlessly transition from javadocs to actual attributes when the time comes. Most of the necessary bits to do this will be in CGLIB, since we have to know the internal structure of the attributes in order to pass them along during transformation. Chris |
