admin@glassfish.java.net

Re: added support for default-config.xml

From: Jerome Dochez <jerome.dochez_at_oracle.com>
Date: Wed, 07 Apr 2010 19:53:12 -0700

On 4/7/2010 7:36 PM, Bill Shannon wrote:
> Jerome Dochez wrote on 04/07/2010 07:23 PM:
>> On 4/7/2010 6:28 AM, Jennifer Chou wrote:
>>>
>>>
>>> On 4/8/2010 9:59 AM, Jerome Dochez wrote:
>>>> I can see 2 disadvantages :
>>>>
>>>> 1. the default-config.xml was separated from the domain.xml meaning
>>>> it was surviving the domain deletion or supporting the multi domain
>>>> situations.
>>>> 2. the deep copy of config element is not implemented, that might
>>>> be more work than adding the support for --target to CLI commands.
>>> I don't know which is more work but if we keep default-config
>>> outside we'll need to do things like.... For create-domain, it will
>>> probably need to make it's own copy of default-config.xml for each
>>> domain.
>> why ? I thought in V2 we had 1 copy of this default-config.xml for
>> all domains (in lib/templates) Is that not the case ?
>
> No, in v2 it's *in* domain.xml, and thus copied to each domain when
> it's created.
got confused then...

so it does not survive domain deletion, it does not allow customizing
multiple domains...

is it really a good idea to keep it so useless ?

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>