[ https://jira.jboss.org/jira/browse/JBAS-7331?page=com.atlassian.jira.plug... ] Jason T. Greene updated JBAS-7331: ---------------------------------- Summary: Switch AS to Parellel Deployment & On-Demand (was: Switch AS to Parellel Deployment) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7331?page=com.atlassian.jira.plug... ] Ales Justin commented on JBAS-7331: ----------------------------------- On-Demand analysis can already be done and properly applied. I suggest using Grapher (with perhaps a few improvements): http://anonsvn.jboss.org/repos/jbossas/projects/mc-tools/grapher/trunk/ Which should help identify the roots, which should then be made lazy (MC <lazy> element usage), while their ancestors should be made on-demand. Wrt parallel deployments, I expect it to only apply it to a few beans. Mostly beans the use jgroups channels, who already provide their own 'parallel' mechanism. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-7331?page=com.atlassian.jira.plug... ] Jason T. Greene updated JBAS-7331: ---------------------------------- Fix Version/s: Unscheduled (was: 6.0.0.M3) Unscheduling due to inactivity. Reassign to a release that you feel comfortable resolving this issue in, or leave as is. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira