Byron Nevins wrote:
> Yes. Come to think of it -- if domain.xml says "foo" and it is sitting
> in directory "goo" -- then
> start-domain "foo" will never work.
>
> I suspect that it was added for the use of instances. The instance
> can't use the trick of looking at the directory name.
>
Please elaborate. I don't understand how this relates to "instances".
> Launcher can enforce this for DAS launching -- fatal error if domain.xml
> value != dir-name
Oops, not needed. Just remove the property from domain.xml and its templates.
It server no useful purpose that I know.
>
>
> Kedar Mhaswade wrote:
>> Lloyd L Chambers wrote:
>>> What if config is:
>>>
>>> /gf/domains/domain-foo/
>>>
>>> and the property says "domain1"?
>>>
>>
>> That should never happen if you don't do something inconsistently.
>>
>> Frankly though, I don't like this property in domain.xml. It affects
>> the relocatability of the domain. The easiest thing to do is name of the
>> domain is the name of its folder.
>>
>> We should take this up after TP-2.
>>
>>> Lloyd