There are tests to catch these negative cases.
http://cvsync.red.iplanet.com/cvsweb/cvsweb.cgi/appserver-sqe/se/admincli/tonga/testbase/reference/configuration/se_ref_man_config_test.cfg?rev=1.10&content-type=text/x-cvsweb-markup&cvsroot=/m/jws
The other case of sharing cluster config is allowed by design in v2 and
its called a shared config.Its not a bug.
A config can be shared by one or more clusters and one or more
standalone instances
-Sankar
On 12/15/10 5:16 PM, Jennifer Chou wrote:
> I verified on v2.1.1, create-instance does not allow 'default-config'
> or 'server-config' for --config. It does however, allow a cluster
> config but I think that must be a bug in v2.1.1? That should not be
> allowed either right?
>
> On 12/15/2010 7:08 PM, Byron Nevins wrote:
>> Those are special configs. You can't use a cluster config either.
>>
>> You can; however, make a snapshot copy of the config "copy-config"
>> and use that.
>>
>>
>> On 12/15/2010 3:57 PM, Anissa Lam wrote:
>>>
>>> I can create the instance successfully and start it.
>>> %asadmin create-instance --node localhost-domain1 --config
>>> default-config TEST
>>>
>>> But in the documentation, it says:
>>> --config
>>> Specifies the named configuration that the instance
>>> references. The configuration must exist and must not be
>>> named default-config or server-config.
>>>
>>> At first, i thought maybe the doc is wrong, but then, I also
>>> remember seeing email that said default-config and server-config
>>> cannot be referenced.
>>> Can someone tell me what is the expected behavior ?
>>>
>>> thanks
>>> Anissa.
>