"flavia.rainone(a)jboss.com" wrote : | This is what I'll do. I'll leave the parent as null in the case above, which will make the exclusion mechanism work. And I'll try to filter out classes belonging to java.* and com.sun.* packages. Every class name that matches those will have an universal CtClass created for it (following the same that is done for primitives in the ClassPool), associated with a null ClassPool. For obvious reasons, I'm not very fond of this approach, but I think it is worth a shot, since it is this or implementing exclusion for classpools. Plus, I think it is the closest we can get to the ClassLoader's behaviour. OK, I see what you mean, and you have a point there. :-) I wouldn't go with this null, but just with a simple CP exclude -- only for tests purposes. e.g. Map the AppCL with DefaultCP, but somehow exclude all but java.* and our test packages. Actually make this exclusion configurable, as we have it in CL/Deployers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269786#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...