On Jul 18, 2012, at 9:04 AM, zeeman wrote: > Hi Anothony, > > What are you excluding? Is that something to improve performance?
Scanning has a huge impact on startup performance and a brief impact on memory. The way the EE specs are written we have to scan all jars "just in case" they might have a class with @Stateless or @ManagedBean or @WebServlet, etc. But if you know which jars are your code and which are third-party libs, you can get a tremendous boost letting us know via the scan.xml file. List the jars where your code lives via the scan.xml file and things will be quite snappy on startup. -David
