Turns out this is a known issue and is logged in Bugzilla under LTW component:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=175814 --- jennie <[EMAIL PROTECTED]> wrote: > Sorry, nevermind about the Xlint messages, they seem > to only control output messages, not the weaver > behavior.. > > It seems that this is is the expected behavior to > use > the resulting invalid bytecode. If it is, is there > consideration to make it configurable (do not use > the > invalid class upon error)? > > Thanks again. > > > --- jennie <[EMAIL PROTECTED]> wrote: > > > Eric, I agree with you that it's good to have the > > error message, but I think the proper behavior is > to > > leave the offending class alone (don't use the one > > with invalid bytecode) after getting the error. > > > > Is there something I'm missing, perhaps an -Xlint > > setting, to tell the weaver to leave main_jsp(or > any > > other class that exceeds the limit during weaving) > > in > > its original state after encountering the error? > > > > I appreciate the help. > > > > --- Eric Bodden <[EMAIL PROTECTED]> > wrote: > > > > > Werll, I guess that's a technical limitation of > > the > > > bytecode weaving > > > approach. Java methods have a size restriction > of > > > 64K. If your method > > > is really large and has a lot of joinpoint > shadows > > > it might sometimes > > > go above this limit during weaving. IMHO giving > > you > > > the error message > > > you are seeing now is a reasonable thing to do. > I > > am > > > not sure if it > > > would be good to just not weave the class in > that > > > case. I rather > > > prefer error messages when something goes wrong. > > But > > > this might depend > > > on the application, I guess... > > > > > > Eric > > > > > > On 08/03/07, jennie <[EMAIL PROTECTED]> > wrote: > > > > Hi there, > > > > > > > > Has anyone gotten a similar error? > > > > > > > > problem generating method > > > > org.apache.jsp.main_jsp._jspService : Code > size > > > too > > > > big: 70282 > > > > > > > > When I tried to decompile with jad, jad also > > > > complained that it couldn't fully decompile > > > > _jspService. The class after weaving seems to > be > > > > corrupted. I'm wondering if the correct > behavior > > > > should be to leave the "too big" class alone > > after > > > > encountering this error? > > > > > > > > I added a comment to this bug that seems > > related: > > > > > > > > > > > > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=138384 > > > > > > > > Thanks for the help. > > > > > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________ > > > > Don't pick lemons. > > > > See all the new 2007 cars at Yahoo! Autos. > > > > http://autos.yahoo.com/new_cars.html > > > > > _______________________________________________ > > > > aspectj-users mailing list > > > > [email protected] > > > > > > > > > > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > > > > > > > ____________________________________________________________________________________ No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started. http://mobile.yahoo.com/mail _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
