[jboss-dev-forums] [JBoss Microcontainer Development POJO Server] - Re: Servlet 3.0 annotation processing requirements

[alesj]

"remy.maucherat at jboss.com" wrote : 
  | a) Per JAR annotation scanning. Due to the fact that the order impacts
  | annotations, the deployer should produce a set of attachements keyed by
  | JAR name for web annotations (like what happens for the web fragments,
  | so that way I can merge the fragment metadata for a given jar, then
  | merge the annotation metadata, then move to the next jar in the order).
  | 
This one doesn't look hard to do.
As we do deployer per all deployment units.
Meaning all you need to do is create 2 new deployers:
* one that would collect the fragment info
* the second one that would apply it

"remy.maucherat at jboss.com" wrote : 
  | b) The ServletContainerInitializer feature. I have no idea how to handle
  | the @HandlesTypes annotation (reminder: the annotation contains a list
  | of classes, and I need to build a set of Class that are in the webapp
  | that implment, extend, or are annotated by any item in the list of
  | classes).
  | 
Yeah, this one sounds pita. Another performance bottleneck on the horizon.

I see 3 ways of doing this:
* part of generic scanning (== preparing info for any resource); hence only a single scan
* on-demand checking (+ some caching); can be done now, but it's slow
* another new Jesper's Papaki project for class info (need to check if this could be part of Reflect)

"remy.maucherat at jboss.com" wrote : 
  | c) The access control annotations were added to Servlet 3.0, and classes that extend HttpServlet can have these annotations as method level annotations (on doGet, doPost, etc; actually all the doXXX methods defined in HttpServlet).
  | 
Easy. Simple AnnotationEnv usage.

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

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