Made names of JMX operations reflect the current limitations

within the webapp.  Currently, we don't support either updating
 a single-webapp, or removing a single-webapp because the GUI
 cannot invite someone to only one webapp within a project.

 Therefore, the JMX calls are "updateAllVirtualWebapps" 
 and "removeAllVirtualWebapps", rather than implying we're 
 more fine-grained that we actually are.  

 The case of removal would be particularly misleading
 because if you thought you could just get rid of single
 webapp, you'd be sadly mistaken.



git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@5072 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
This commit is contained in:
Jon Cox
2007-02-08 05:39:04 +00:00
parent d851541e93
commit d855bb345b

View File

@@ -94,10 +94,10 @@ public class AVMSubmitTransactionListener extends TransactionListenerAdapter
// Only update staging if necessary
if ( requiresUpdate != null )
{
vServerRegistry.webappUpdated( requiresUpdate.getDestinationVersion(),
requiresUpdate.getDestinationPath(),
true
);
vServerRegistry.updateAllWebapps( requiresUpdate.getDestinationVersion(),
requiresUpdate.getDestinationPath(),
true
);
}
// Remove virtual weapps from workflow sandbox
@@ -109,7 +109,7 @@ public class AVMSubmitTransactionListener extends TransactionListenerAdapter
// look at the 1st difference
AVMDifference d = stagingDiffs.iterator().next();
vServerRegistry.webappRemoved( d.getSourceVersion(), d.getSourcePath(), true );
vServerRegistry.removeAllWebapps( d.getSourceVersion(), d.getSourcePath(), true );
}