"adrian(a)jboss.org" wrote : | My concern was that you had one class for all deployments defined against the | "first" classloader, which could later get redeployed and thus cause that | classloader to leak. | That was the case before https://jira.jboss.org/jira/browse/JBAS-5505 "adrian(a)jboss.org" wrote : | But it does sound like you are generating instrumented classes for things like | java.util.ArrayList in every deployment which could be minimized if they were shared | in the AOP classloader. I get your point about introductions, but isn't that an edge case? Yes, that is an optimization that can be done View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206647#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...