[jboss-dev] Papaki Annotation Scanning Requirements

[Carlo de Wolf]

I haven't worded it yet for a definitive requirement.

There is a subtle difference between scanning & processing. What I don't 
want is unnecessary processing if a descriptor is metadata complete.
Note that this only goes for EJB annotations, other annotation 
processing is left beyond scope.

EJB 3.1-fr 20.5.2 .war Deployment Descriptor and Annotation Processing
Table 26 describes the requirements for determining when to process 
annotations on the enterprise bean classes of a .war. If the .war 
contains an ejb-jar.xml file the deployment tool will process 
annotations unless the ejb-jar.xml has been marked metadata-complete. If 
the .war does not contain an ejb-jar.xml file, the deployment tool will 
process annotations unless the web.xml is marked metadata-complete or 
its version is prior to web-app_2_5.

Table 26 .war Annotation Processing Requirements for enterprise beans
ejb-jar.xml
	ejb-jar.xml
metadata-complete?
	web.xml
	web.xml
metadata-complete?
	process
annotations?
ejb-jar_3_x
	Yes
	N/A
	N/A
	No
ejb-jar_3_x 	No
	N/A
	N/A
	Yes
none
	N/A
	web-app_3_0 or
web-app_2_5
	Yes
	No
none
	N/A
	web-app_3_0 or
web-app_2_5 	No
	Yes
none
	N/A
	web-app_2_4 or
earlier
	N/A
	No
none
	N/A
	none
	N/A
	Yes


Carlo

On 10/29/2009 08:39 PM, Dimitris Andreadis wrote:
> Please edit the wiki page and add your annotation scanning requirements/usecases:
>
> http://www.jboss.org/community/wiki/PapakiAnnotationScanningRequirements
>
> "Annotation scanning has a considerable impact in AS deployment and boot time performance.
> There are several subsystems that need to process annotations, for example EJB3, JCA, Web
> Services, JBoss Web, JPA, Seam, etc. and that often results either in inefficient annotation
> scanning implementations, extraneous classloading and multiple passes over the same jar files.
>
> The goal of the Papaki project (formerly JBoss Annotations) is to unify annotation scanning,
> so that it can be performed efficiently and in one pass, with the various subsystem pulling
> annotation information from the Papaki service, thus improving deployment and boot times.
>
> The purpose of this page is to collect requirements from all the projects that would be
> interested in plugging into this service, so that we can come up with a comprehensive API
> that can serve all the major use cases."
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-development/attachments/20091111/2a8a5c94/attachment.html