Re: [aspectj-dev] Minor API request for BcelObjectType

[Andrew Clement <CLEMAS@xxxxxxxxxx>]

Just before we raise an enhancement
request and look at doing this for you, I'd be interested in a bit more
detail.  You mention 'our own way of using AspectJ', can you give
any more details?  It's just that if some proposed improvements to
BcelObjectType (or the management of BcelObjectType objects) would be beneficial
to everyone, I'd be keen to roll them directly into the AspectJ codebase.

thanks,
Andy.
---
Andy Clement
AspectJ Committer
clemas@xxxxxxxxxx

"Larry Zhou" <lzhou@xxxxxxxxxx>
Sent by: aspectj-dev-admin@xxxxxxxxxxx

06/01/2005 22:03

Please respond to
aspectj-dev@xxxxxxxxxxx

To	<aspectj-dev@xxxxxxxxxxx>
cc
Subject	[aspectj-dev] Minor API request for BcelObjectType

Hi,

We have been using AspectJ successfully in our development. AspectJ helps us a great deal. Thanks.

We had this memory issue with AspectJ, since every JavaClass instance was kept live all the time. To put it in real number, for example, to start weblogic app server 8.1.3 for integration, the extra memory usage by AspectJ was about 150M to 180M.

We would like to request the following changes for modifiers in BcelObjectType.java, ( No functionality change at all )
1) first 15 private data members changed from private to protected
2) constructor changed from package access to protected.
3) method getJavaClass changed from package to public. ( Even setJavaClass is public )

That way, we can subclass BcelObjectType, make it MyBcelObjectType, then kill this object when appropriate due to our own way of using AspectJ, we are able to cut the memory usage by 90% to around 15M now.

Let me know if you have any questions about my request.

Thanks a lot,

Larry