And, just three months later, there it is! :-) I just committed a batch of code modifications that now ensure that there are no undue strong references to Class objects anywhere in the code. The MOP framework should now no longer interfere with the lifecycle of the classes it comes in contact with.
Attila. -- home: http://www.szegedi.org weblog: http://constc.blogspot.com On 2007.12.07., at 21:50, Attila Szegedi wrote: > > On 2007.12.07., at 19:32, Charles Oliver Nutter wrote: > >> >> Attila Szegedi wrote: >>> A memory leak? >>> >>> marshalTypes certainly isn't. It might retain Class objects used in >>> argument types of the overloaded method, but those can't be unloaded >>> anyway until the class that the method itself belongs could be >>> unloaded. >> >> Which presumably leads to the marshalTypes going away as well, in a >> perfect world...yes? > > It will, after I rewrite the "mops" map in BeansMetaobjectProtocol > to use soft references. Right now it doesn't, but that's definitely > on my short-term TODO list once the core implementation stabilizes. > Ability to play nicely in systems that unload/reload classes is > essential for most enterprise environments, so I'm taking that > seriously. > > Attila. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
