This topic has not yet been written. The content below is from the topic description.
Domains Detectors have the ability to accept multiple domains. What domains that the detector will accept as viewable can either be set programmatically via the method: public void setConfiguration(org.w3c.dom.Element xml) or by adding to jboss-service.xml configuration for the detector. The domains that the detector is currently accepting can be retrieved from the method: public org.w3c.dom.Element getConfiguration() The configuration xml is a MBean attribute of the detector, so can be set or retrieved via JMX. There are three possible options for setting up the domains that a detector will accept. The first is to not call the setConfiguration() method (or just not add the configuration attribute to the service xml). This will cause the detector to use only its domain and is the default behavior. This enables it to be backwards compatible with earlier versions of JBoss Remoting (JBoss 4, DR2 and before). The second is to call the setConfiguration() method (or add the configuration attribute to the service xml) with the following xml element: domain1 domain2 where domain1 and domain2 are the two domains you would like the detector to accept. This will cause the detector to accept detections only from the domains specified, and no others. The third and final option is to call the setConfiguration() method (or add the configuration attribute to the service xml) with the following xml element: This will cause the detector to accept all detections from any domain. By default, remoting detection will ignore any detection message the it receives from a server invoker running within its own jvm. To disable this, add an element called 'local' to the detector configuration (alongside the domain element) to indicate should accept detection messages from local server invokers. This will be false by default, so maintains the same behavior as previous releases. For example: domain1 domain2 An example entry of a Multicast detector in the jboss-service.xml that accepts detections only from the roxanne and sparky domains using port 5555, including servers in the same jvm, is as follows: 5555 roxanne sparky