Ah, you're looking for a name for the entire *domain* as opposed to the
domain controller itself. That wouldn't have any particular use within a
domain itself, but could certainly be helpful for tooling that manages
multiple domains.
Heiko Rupp -- do you want this? That would raise the priority on it.
I think the default value would have to be 'undefined', i.e. null. We
can create default names for hosts, using machine data, but there's no
equivalent for a domain. And I don't want to force people to name domains.
On 4/2/12 9:30 AM, ssilvert(a)redhat.com wrote:
OK. So can you have more than one host per domain controller
instance?
If so then there should still be a unique name in the<domain> tag.
This list result suggests that indeed, more than one host is allowed,
but I'm really not sure.
/host=*/:read-attribute(name=name,include-defaults=true)
{
"outcome" => "success",
"result" => [{
"address" => [("host" => "master")],
"outcome" => "success",
"result" => "master"
}]
}
On 3/30/2012 10:53 AM, Brian Stansberry wrote:
> In host.xml:
>
> <host name="Michael" ...
>
> On 3/30/12 8:26 AM, ssilvert(a)redhat.com wrote:
>> In the first element of standalone.xml I can rename my server<server
>> name="George" ...
>>
>> But for a domain controller, I don't see any way to give it a name. It
>> has no name at all. Is there any reason for this?
>>
>> It would be helpful to give your domain controller a name. That way if
>> you have more than one you can tell which one you are talking to over
>> the management interface.
>>
>> Stan
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat