On 01/21/2010 11:19 AM, Rémy Maucherat wrote:
On Thu, Jan 21, 2010 at 4:18 PM, Brian Stansberry
<brian.stansberry(a)redhat.com> wrote:
> One thing I'm looking at is tagging the console's web.xml as metadata
> complete. I'm seeing a ton of logging from WarAnnotationMetaDataDeployer.
Disabling that does not really disable annotation scanning anymore: it
only disables annotations which add to the web.xml metadata (= mostly
the new ones from Servlet 3.0). Also, the optimized annotation scanner
is not used yet, since it does not meet the Servlet 3.0 requirements
yet (if this has changed, let me know).
However, since classloading would happen anyway, the scanning cost is
not a total showstopper.
I got 2 secs from adding metadata-complete=true. But that was hardly a
scientific test.
Anyway, IMO just as a general practice anything we ourselves deploy
should be metadata complete. We should optimize our stuff for boot perf,
not for convenience of our own folks developing it.
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat