Re: [aspectj-users] Ability to exclude class loader from creating weaver

[Andy Clement <andrew.clement@xxxxxxxxx>]

Hey Sergei,

I just resurrected the changes and committed them into master, they will be in 1.7.4. Updated usage instructions in the bug report, although bugzilla appears to be on a go slow so I might not be able to get my update text through until the morning. If you are planning on using it imminently I can create a dev build for you, let me know.

cheers,

Andy

On 29 July 2013 10:16, Sergei Babovich <sbabovich@xxxxxxxxxxxxxx> wrote:

Hi,

There is an existing fix https://bugs.eclipse.org/bugs/show_bug.cgi?id=368046 which was planned to become part of 1.7.0 (but it did not happen). It is a significant improvement for web apps with the large number of jsps. Each jsp page has its own class loader. Without ability to exclude classloaders complex app with multiple thouthand of jsps wastes a lot of memory on unused weavers (we saw up to 100M).  Are there still plans to include it into the next patch? Any timeframe?

Thank you,
Sergei
This e-mail message and all attachments transmitted with it may contain privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message, all attachments and all copies and backups thereof.

_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users