Yes, I should have been more clear: it's probably easy to make such a
change, but needs a lot of study.
I'm just thinking ahead to clustering, where inertia is likely to
repeat the past headaches in which a non-clustered server automates
the references and a clustered one does not, wreaking havoc with API
consistency.
Lloyd
On Jun 9, 2009, at 10:10 AM, Kedar Mhaswade wrote:
> Right. Later. Needs lot of thought exercise.
>
> Lloyd Chambers wrote:
>> IMO, it would be great if we dumped that model and made the
>> <config> be contained by a <server> or <cluster>. That would still
>> yield the sharing benefits of most deployments. Coupled with a
>> "clone config into server or cluster"...
>> Lloyd
>> On Jun 9, 2009, at 4:39 AM, Kedar Mhaswade wrote:
>>> Correct.
>>> And for single instance product (i.e. what GFv3 is going to be), the
>>> boundaries between a "server" and its "config" should be as blur
>>> as possible.
>>>
>>> Over the years, I have gathered that, people have difficulties
>>> understanding the
>>> subtle relationship between "server", its "config" and the
>>> reference mechanism.
>>>
>>> -Kedar
>>>
>>> Sankar Neelakandan wrote:
>>>> Hi Anissa,
>>>> There is no other command to create system properties. I guess
>>>> if the --target allows server-config as a valid target then it
>>>> can be created under server-config. Right now the command doesn't
>>>> support server-config as a valid target. Since "server" is the
>>>> only instance using the server-config what other advantage do you
>>>> gain with creating system properties under server-config ?.
>>>> thanks
>>>> Sankar
>>>> for this command then
>>>> Anissa Lam wrote:
>>>>> Hi,
>>>>> I have a question regarding the CLI create-system-properties
>>>>> command in v3.
>>>>>
>>>>> NAME
>>>>> create-system-properties - adds or updates one or more
>>>>> system properties of the domain, configuration, cluster, or
>>>>> server instance
>>>>>
>>>>> SYNOPSIS
>>>>> create-system-properties
>>>>> [--terse={true|false}][ --echo={true|false} ]
>>>>> [ --interactive={true|false} ] [ --host host]
>>>>> [--port port] [--secure| -s ] [ --user admin_user]
>>>>> [--passwordfile filename] [--help]
>>>>> [ --target target_name]
>>>>> [name=value)[:name=value]*]
>>>>>
>>>>> This only create the system property under <server>. I can't
>>>>> figure out a way to create it under <server-config>. Can
>>>>> someone help me ?
>>>>> Am i suppose to use another CLI command to create system-
>>>>> property under config ?
>>>>>
>>>>> thanks
>>>>> Anissa.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>>>>> <mailto:admin-unsubscribe_at_glassfish.dev.java.net>
>>>>> For additional commands, e-mail: admin-
>>>>> help_at_glassfish.dev.java.net <mailto:admin-help_at_glassfish.dev.java.net
>>>>> >
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net <mailto:admin-unsubscribe_at_glassfish.dev.java.net
>>>> >
>>>> For additional commands, e-mail: admin-
>>>> help_at_glassfish.dev.java.net <mailto:admin-help_at_glassfish.dev.java.net
>>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net <mailto:admin-unsubscribe_at_glassfish.dev.java.net
>>> >
>>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>> <mailto:admin-help_at_glassfish.dev.java.net>
>>>
>> Lloyd Chambers
>> lloyd.chambers_at_sun.com <mailto:lloyd.chambers_at_sun.com>
>> GlassFish Team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
Lloyd Chambers
lloyd.chambers_at_sun.com
GlassFish Team