&quot;scott.stark(a)jboss.org&quot; wrote : | The only possible usage would be to obtain package annotations, but then is that really an empty package? | No there is a package-info.class anonymous wrote : | This really seems like a management interface issue where I want to be able to ask, what are the package export filters that apply to the class loader. From that perspective, the includedExport is just an alias for a type of capability (package, custom). | I'm working on it. I can't do everything at once. ;-) Once I've done the management features you requested, then I'll add ManagedOperations/Statistics to the ClassLoadingMetaData ManagedObject. This can include the packages exported by a classloader, classes/resources loaded, etc., although I'm only going to do a basic set for the initial release as a "proof of concept", then you, me or somebody else can add extra features. anonymous wrote : | However, since you can't use a namespace in an attribute value, how would you specify something other than a package filter? Given that, I would say the includedExport is only used for package filtering, and we can decide if we want better detection of conflicting statements that end up in an empty export set in the management interface. | I haven't enabled the full ClassFilter functionality in the xml or ManagedObject yet, because the ClassFilter stuff needs fixing to be serializable. I'll do them as elements so you can properly customize it. With xml wildcards, etc. to define your own. WARNING THIS DOES NOT EXIST YET e.g. something like: | <classloading ...> | <!-- builit in--> | <include type="RegExp">javax\.ejb\..+</include> | <!-- or equivalently --> | <include type="Glob">javax.ejb.**</include> | <!-- user defined --> | <include type="Custom"><myfilter xmlns="whatever" ..../></include> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131438#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...