<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
        <table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
                <tbody>
                        <tr>
                                <td>
                                        <table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
                                                <tbody>
                                                        <tr>
                                                                <td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
                                                                        <h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
                                                                        <!-- To have a header image/logo replace the name below with your img tag -->
                                                                        <!-- Email clients will render the images when the message is read so any image -->
                                                                        <!-- must be made available on a public server, so that all recipients can load the image. -->
                                                                        <a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
                                                                </td>
                                                        </tr>
                                                        <tr>
                                                                <td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Infinispan Subsystem Management API
</h3>
<span style="margin-bottom: 10px;">
new comment by <a href="http://community.jboss.org/people/brian.stansberry">Brian Stansberry</a> <a href="http://community.jboss.org/docs/DOC-17351#comment-8204">View all comments on this document</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>On the multi-step approach, the CLI allows batching of commands, so the series of commands listed above could be executed as an atomic batch. (Internally, a single operation, named "composite" is sent, with a single parameter whose value is a DMR list, each element of which is the DMR for one of the steps.)</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>When an operation executes, it is done in stages -- first is a MODEL stage where updates are applied to the configuration model, then a RUNTIME stage, where updates are applied to runtime services. Finally a VERIFY stage where container services are known to be settled and assertions about their state can be done. With a composite operation, the MODEL stage for each step is done before the RUNTIME stage for the 1st step begins. The effect of this is the RUNTIME part of the 1st step can see the model changes made in the MODEL stage of all the steps.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The other thing that can be useful is having the OperationStepHandler for the 1st step's RUNTIME stage itself add another RUNTIME step. The RUNTIME step will be added at the end of the list of RUNTIME steps and will thus execute after all the step's RUNTIME stage. So, work done by those steps can be visible to this final step.</p></div>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>