[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Too strict pattern matching in PackageClassFilter

[adrian@jboss.org]

"scott.stark at jboss.org" wrote : That looks to be by design. We should have a RecursivePackageClassFilter or allow package wildcards like javax.servlet.* to indicate the javax.servlet package or any of its subpackages.
  | 

Yes. Obviously the semantics of filteredPackages on the WarClassLoaderDeployer
is different to ClassLoadingMetaData's excludedPackages.
i.e. it is recursive rather than an explicit list of packages

anonymous wrote : 
  | I'll have to look at how the filteredPackages information is incorporated into the class loader model because it could simply be that is where the behavior could be extended.
  | 

The WarClassLoaderDeployer simply sets the list of explicit packages to exclude.
      classLoadingMetaData.setExcludedPackages(filteredPackages);

A simple fix would be to use the option to set the filter directly.
      classLoadingMetaData.setExcluded(new RecursivePackageFilter(filteredPackages));

except that no such ClassFilter implementation currently exists.

It should be easy to create one by copying the PackageClassFilter
but change it to use the regular expressions like those in the JavaOnlyClassFilter.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207661#4207661

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207661