Hi! The proxy-classes are generated and held for each Bean. New boot, new Bean..
And we use the ClassLoader of the class currently. I already suggested such interface in a previous jira issue [1]. LieGrue, strub [1] https://issues.apache.org/jira/browse/OWB-931 On Sunday, 19 October 2014, 13:43, Romain Manni-Bucau <[email protected]> wrote: > > >Hi > >tck uses arquillian so 80% of the time apps have an embedded >classloader around SW archive. Then OWB uses class classloader to >define the proxy (app loader for most of them)...in tomee we don't >finish tck cause we explode perm gen space. I fixed it on tomee side >but I guess OWB has the same issue. We should use the application >loader and not the class one. > >Do we introduce a SPI for it? >ProxyClassLoaderProvider#findClassLoader(Class) or something like >that? > > >Romain Manni-Bucau >@rmannibucau >http://www.tomitribe.com >http://rmannibucau.wordpress.com >https://github.com/rmannibucau > > >
