metadata-complete was added to admin-console web.xml.
https://jira.jboss.org/jira/browse/EMBJOPR-277
It will be in the tagged EMBJOPR release for M2.
Shelly
----- Original Message -----
From: "Jaikiran Pai" <jpai(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Thursday, February 11, 2010 10:37:46 AM GMT -05:00 US/Canada Eastern
Subject: Re: [jboss-dev] M2 Boot time
Yeah, over IRC, Brian pointed me to that previous discussion.
-Jaikiran
Rémy Maucherat wrote:
On Thu, Feb 11, 2010 at 3:54 PM, Jaikiran Pai <jpai(a)redhat.com>
wrote:
> Did a quick round of profiling. Now that the admin-console deployment is
> lazy and separate from the server bootup, it was easier to find out
> what's taking time.
>
> For first access (*not* the login), turns out, the WARAnnotationDeployer
> spends almost 41 % percent of the time processing the war - mainly in
> getClasses() which starts looking for classes in the war file for
> annotation scanning. The admin-console.war/WEB-INF/lib has jar totaling
> to10 MB in size. I remember, there was discussion to add
> metadata-complete, to the web.xml of this war. I don't see it in the
> web.xml. Also, adding that hadn't shown any performance improvements.
> Looking at the WarAnnotationMetaDataDeployer.deploy(...), or other
> methods in there, i don't see any check for metadata-complete.
As previously discussed, metadata-complete cannot be used for this usage.
Rémy
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development