Hi, There is no imposed limit on aspect weaving number, *but* you might hit the limits that are not handled cleanly. For example method code size (which is 64k IIRC) if you weave in too many invocations of advice. I have never seen this problem manifest as a key size problem though - if you blow the method limit you should get an error about code size.
Although, I suppose it is possible that as a list of aspects is included in one of the class file attributes it *could* be the case that if your aspects have long names or are in a deep package hierarchy that the name will blow one of the attribute size limits (also 64k), which *might* manifest like this. Does it behave differently if you shorten the package name or shorten the aspect names? cheers, Andy On 27 April 2013 09:10, aryenneb <aryen...@hotmail.com> wrote: > Hi, > Sorry guys for opening up this thread again. But my problem is still not > solved and I am trying to learn AspectJ. I am a real newbie so please > excuse the dumb questions. Ok, so my project works with a small number of > input files, with no problems. I do not need to use the compiler option > -Xset:overWeaving=true suggested; since when I do, the key conflict error > disappears, but nothing else works. > > I just realized that the problem seems to be with the number of aspects > that > have to be woven. When I have up to about 50 aspects, there is no problem, > the code runs correctly and all of the weaving occurs smoothly. However, > when I try to scale my project and have about 200 aspects that's when the > key conflict error pops up. Now these are small aspects. Before I was > generating fewer, but larger aspects and there were memory problems. By > reducing the aspect size, I do not have any more memory issues; but weaving > seems to be a problem. > > My code compiles, but when I try to run it, I get the error: Aspectj > error:Internal compiler error: java.lang.RuntimeException: key not found in > wovenClassFile at > org.aspectj.weaver.WeaverStateInfo.findEndOfKey(WeaverStateInfo.java:408). > Adding the non-standard compiler option -Xset:overWeaving, gets rid of the > error but causes the code to work incorrectly. I am now wondering if there > is a limit to the number of aspects allowed in an AspectJ project? I have > been 'Googling' it for a while with no success. > > Any suggestions will be greatly appreciated. > Thank you. > Aryenne > > > > -- > View this message in context: > http://aspectj.2085585.n4.nabble.com/Aspectj-error-Internal-compiler-error-java-lang-RuntimeException-key-not-found-in-wovenClassFile-at--tp4650879p4650917.html > Sent from the AspectJ - users mailing list archive at Nabble.com. > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/aspectj-users >
_______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users
