"scott.stark(a)jboss.org" wrote : Rather than looking at parallel deployment
first, I think the consensus was to look at using on-demand as the first step in improving
the boot times.
My current list, in no particular order.
* use On_Demand where it makes sense (X)
* analyze our services, add @MCAnnotations, @DisableAOP({DisableType.?}) (Y)
* federated resources lookup
** usage of AnnotationEnvironment
** fix Metadata's paradigm
*** only asking for what it needs, not checking all against some constraints
** cache other resources, as we're doing the scanning anyway
** limit what we're scanning
*** jboss-scanning.xml
*** (X) jboss-classloading.xml
* usage of (X) will limit the class sharing/lookup == speed up
* profile service loading profiles on demand
** e.g. usage @MDR enterprise bean triggers JMS profile load
* parallel deployment
* xyz ...
For (X) and (Y) I'm looking into hacking some MC based tool
to help us identify potential services that could use this, either (X) or (Y).
I need to check how I can re-use Tattletale to help me.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233985#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...