"alesj" wrote : "emuckenhuber" wrote : I guess it could also make sense to see if we can reuse this annotation index in MDR as well? | | | Yup. | I guess AE really belongs into Papaki. At least the spi/api/interfaces. | (and afair my code, it doesn't have any Deployers dependencies) | It most probably should be part of the AS integration, as we only add it to the DU we don't need the deployers to depend on it as well. "alesj" wrote : | "emuckenhuber" wrote : | | Beside that we would need a better programmatic API for excluding resources from scanning. I think this is actually the most important piece we have to do, as not doing any annotation scanning at all would most probably be faster than indexing :) | | | | So we would need to create a ScanningMetaData when e.g. JBossEjbMetaData.isMetaDataComplete(). This then would exclude all non EE5 deployments from annotation scanning without a separate jboss-scanning.xml. As far as i can remember for servlet 3.0 we would need be able to exclude resources on .jar basis as well. | This should all be a part of ScanningMetaData - some helper class; e.g. like BMDBuilder --> SMDBuilder. | It would then be trivial to build ScanningMetaData and place it into DU. | | And then PapakiDeployer should take ScanningMetaData into an account while building AE. Yeah something simple like that should be enough. We could also add some simple deployers to the 5_x branch - at least generating a empty ScanningMetaData for isMetaDataComplete() does not require Papaki. This could speed up legacy deployments quite a bit, as we wouldn't process the already scanned annotations anyway. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255072#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...