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
-- Eric Bodden Sable Research Group McGill University, Montréal, Canada _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
