<!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/scott.stark%40jboss.org">Scott Stark</a> in <i>Management Development</i> - <a href="http://community.jboss.org/message/536133#536133">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>There is always scoping as we need to know how a property specified at the cluster or domain level applies to the server as in the example of system or jvn properties. There its straightforward; the more specific value overrides the more general.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>We have not talked about cluster or admin domain metadata, I mean a, so I view your example as just introducing that notion.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The various domain model elements map onto a ManagedComponent in a way that need to be clearly defined. Logically I stil think about it in terms of scopes that have to be applied to a piece of deployment metadata, and each layer adds the opportunity to specify a default that can be overriden by a more specific value.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>So, looking at your little fragment, a clustered-service at at group (which I'm thinking of as admin-domain notion), is a specification of clustering aspects that hae to be applied to a bean or spec component. The resource element is a profile default saying that the profile that maps to the "</p><pre><code>Production</code>" group should include a "<code>Production DB" jca factory.<br/></code></pre><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>This is our initial major challenge to moving to the domain model. We need a mapping from domain metadata namespaces onto a ManagedComponent/ManagedProperty. There can be multiple domain metadata namespaces mapping onto a given ManagedComponent/ManagedProperty.</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/536133#536133">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>