<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
I haven't worded it yet for a definitive requirement.<br>
<br>
There is a subtle difference between scanning & processing. What I
don't want is unnecessary processing if a descriptor is metadata
complete.<br>
Note that this only goes for EJB annotations, other annotation
processing is left beyond scope.<br>
<br>
EJB 3.1-fr 20.5.2 .war Deployment Descriptor and Annotation Processing<br>
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.<br>
<br>
Table 26 .war Annotation Processing Requirements for enterprise beans<br>
<table width="100%" border="1" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td valign="top">ejb-jar.xml<br>
</td>
<td valign="top">ejb-jar.xml<br>
metadata-complete?<br>
</td>
<td valign="top">web.xml<br>
</td>
<td valign="top">web.xml<br>
metadata-complete?<br>
</td>
<td valign="top">process<br>
annotations?<br>
</td>
</tr>
<tr>
<td valign="top">ejb-jar_3_x<br>
</td>
<td valign="top">Yes<br>
</td>
<td valign="top">N/A<br>
</td>
<td valign="top">N/A<br>
</td>
<td valign="top">No<br>
</td>
</tr>
<tr>
<td valign="top">ejb-jar_3_x</td>
<td valign="top">No<br>
</td>
<td valign="top">N/A<br>
</td>
<td valign="top">N/A<br>
</td>
<td valign="top">Yes<br>
</td>
</tr>
<tr>
<td valign="top">none<br>
</td>
<td valign="top">N/A<br>
</td>
<td valign="top">web-app_3_0 or<br>
web-app_2_5<br>
</td>
<td valign="top">Yes<br>
</td>
<td valign="top">No<br>
</td>
</tr>
<tr>
<td valign="top">none<br>
</td>
<td valign="top">N/A<br>
</td>
<td valign="top">web-app_3_0 or<br>
web-app_2_5</td>
<td valign="top">No<br>
</td>
<td valign="top">Yes<br>
</td>
</tr>
<tr>
<td valign="top">none<br>
</td>
<td valign="top">N/A<br>
</td>
<td valign="top">web-app_2_4 or<br>
earlier<br>
</td>
<td valign="top">N/A<br>
</td>
<td valign="top">No<br>
</td>
</tr>
<tr>
<td valign="top">none<br>
</td>
<td valign="top">N/A<br>
</td>
<td valign="top">none<br>
</td>
<td valign="top">N/A<br>
</td>
<td valign="top">Yes<br>
</td>
</tr>
</tbody>
</table>
<br>
Carlo<br>
<br>
On 10/29/2009 08:39 PM, Dimitris Andreadis wrote:
<blockquote cite="mid:4AE9EF6E.1080805@redhat.com" type="cite">
<pre wrap="">Please edit the wiki page and add your annotation scanning requirements/usecases:
<a class="moz-txt-link-freetext" href="http://www.jboss.org/community/wiki/PapakiAnnotationScanningRequirements">http://www.jboss.org/community/wiki/PapakiAnnotationScanningRequirements</a>
"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
<a class="moz-txt-link-abbreviated" href="mailto:jboss-development@lists.jboss.org">jboss-development@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jboss-development">https://lists.jboss.org/mailman/listinfo/jboss-development</a>
</pre>
</blockquote>
<br>
</body>
</html>