[jboss-dev-forums] [JBoss Microcontainer Development POJO Server] - Re: Adding a ClassLoader import exclusion filter

[jason.greene@jboss.com]

"alesj" wrote : You can already do all of these things, 
  | most of if just requires proper ClassLoadingMetaData / jboss-classloading.xml configuration.
  | 

AFAICS a deployment can only exclude classes that it contains (excludes) or that it exports (excludeExport). A deployment could achieve this by defining all the package requirements for every EE and JBoss API it uses, however this could end up being overly verbose compared to a simple exclusion. What I am talking about would be something like a new excludeImport value which would take precedence over any import (either importAll or via module imports). However, I don't want to add it if this would violate the intentions of the design, or if you guys think it would be a bad practice. 

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

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