<!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">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;">
To scope or not to scope (domain.xml)
</h3>
<span style="margin-bottom: 10px;">
reply from <a href="http://community.jboss.org/people/bstansberry%40jboss.com">Brian Stansberry</a> in <i>Management Development</i> - <a href="http://community.jboss.org/message/536159#536159">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>I agree that a given piece of metadata only existing one place in the model should be the pattern. The template idea makes that relatively painless.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>An exception I could see to that would be an element that represents a more general notion of a system property. Formalize the system property substition concept with an element that represents a variable that could be referenced elsewhere.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>As to the homogeneous group notion, my thoughts on this were to have a "profile" notion that would encapsulate most of the common configuration. Then clusters, groups or standalone servers would declare what profile they run. This is copied from something I whipped up on a plane to show people in recent clustering meetings, so take it as an illustration only:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><pre class="jive-pre"><code class="jive-code jive-xml"><span class="jive-xml-tag"><domain></span>
   <span class="jive-xml-tag"><profile name=”jee”></span>.... define a set of capabilities, configuration thereof<span class="jive-xml-tag"></profile></span>
   <span class="jive-xml-tag"><profile name=”datagrid”></span>.... define a different set of capabilities<span class="jive-xml-tag"></profile></span>
   <span class="jive-xml-tag"><profile name=”XYZ"></span>.... define a third set of capabilities<span class="jive-xml-tag"></profile></span>
   <span class="jive-xml-tag"><cluster name=”JEECluster” mcast_addr=”234.5.6.7” default_stack=”udp” profile=”jee”/></span>
   <span class="jive-xml-tag"><cluster name=”DataGrid” mcast_addr=”235.6.7.8” default_stack=”udp” profile=”datagrid”/></span>
   <span class="jive-xml-tag"><server-group name="SomeGroup"></span>
      <span class="jive-xml-tag"><server-group-property name="foo"></span>bar<span class="jive-xml-tag"></server-group-property></span>
   <span class="jive-xml-tag"></server-group></span>
   <span class="jive-xml-tag"><server name=”jee1” bind_address=”192.168.0.100”></span>
       <span class="jive-xml-tag"><cluster-ref name=”JEECluster” cluster_address=”10.0.0.100”/></span>
   <span class="jive-xml-tag"></server></span>
   <span class="jive-xml-tag"><server name=”jee2” bind_address=”192.168.0.101”></span>
      <span class="jive-xml-tag"><cluster-ref name=”JEECluster” cluster_address=”10.0.0.101”/></span>
   <span class="jive-xml-tag"></server></span>
   <span class="jive-xml-tag"><server name=”grid1” bind_address=”192.168.0.102”></span>
       <span class="jive-xml-tag"><cluster-ref name=”JEECluster” cluster_address=”10.0.0.102”/></span>
   <span class="jive-xml-tag"></server></span>
   <span class="jive-xml-tag"><server name=”grid2” bind_address=”192.168.0.103”></span>
      <span class="jive-xml-tag"><cluster-ref name=”JEECluster” cluster_address=”10.0.0.103”/></span>
   <span class="jive-xml-tag"></server></span>
   <span class="jive-xml-tag"><server name=”somegroupA” bind_address=”192.168.0.104”></span>
      <span class="jive-xml-tag"><server-group-ref name=”SomeGroup”/></span>
   <span class="jive-xml-tag"></server></span>
   <span class="jive-xml-tag"><server name=”somegroupB” bind_address=”192.168.0.105”></span>          <span class="jive-xml-tag"><server-group-ref name=”SomeGroup”/></span>
   <span class="jive-xml-tag"></server></span>
  
   <span class="jive-xml-tag"><server name=”standalone” bind_address=”192.168.0.106”></span>
      <span class="jive-xml-tag"><profile-ref name=”XYZ”/></span> <span class="jive-xml-comment"><!-- Standalone server --></span>
   <span class="jive-xml-tag"></server></span>
<span class="jive-xml-tag"></domain></span></code></pre><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>A "cluster" element defines some clustering-related configuration. A server-group is a general group but not a cluster. Not sure exactly what that would be; but I threw it in, as Rich Sharples mentioned it had proved useful.  Then a standalone server.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Jason, I'm not sure what a "clustered-service" is.</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="http://community.jboss.org/message/536159#536159">going to Community</a></p>
        <p style="margin: 0;">Start a new discussion in Management Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2107">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>