Having to list the package names in the "include" attribute is a pain... The main intention for that is to not have to inspect every single loaded class when loadtime weaving is used. I've not thought this through 100%, but there will be a lot less beans than loaded classes, so I am thinking of making this a bit more automatic by modifying the AOPDependencyBuilder to not use the include/exclude test. If the class is "excluded" but has aspects, then add this class to the list of "included" classes, so that when we come to the instantiate phase we get the aspects generated as expected. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010211#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...