anonymous wrote : | Papaki should actually be more minimal than it is. The indexes should be built by directly examining the file. Think about it - possibly every class in every JAR that is ever deployed may end up being read by this. There is absolutely no way that reflection is going to cut it performance-wise, nor do I think Javassist will suffice. | The indexer in Papaki builds an index over where annotations are located within the .class or .jar file. If the indexer is present, but is empty the framework will skip the entire annotation parsing stage. If an index is present, but contains annotation metadata only the part of the .class file where the annotation is located is scanned. The annotations themself can't be located in the metadata as they are not serializable, but the all the metadata about them can. Furthermore the scanner can be configured to only scan the part of the classes you are interested in - f.ex. if an annotation only can be located on a public class - at class level - then all non-public classes, all fields, all constructor, all methods and all parameters are skipped. HTH View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261275#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...