Kedar,
Nothing to reconsider, I believe we are on course for this next
release as your CLI spec suggests.
A vision should not be reconsidered when one can do better, even if it
must be deferred.
This is not about configuration only. Pathnames are a completely
general tool to access any entity in the system, namely MBeans, but
anything else also.
Lloyd
On Mar 24, 2009, at 3:22 PM, Kedar Mhaswade wrote:
> Lloyd,
>
> I understand the motivation. But we have to pick something
> here. I can bring this up in the arch review of CLI spec, but
> it seems to me that higher level commands are a must. Remember,
> not all configuration we have comes from an abstract hierarchy
> of config/other objects. I request you not to concentrate just
> on domain.xml. I however, tend to agree with you for the
> configuration that goes to domain.xml -- it is best served
> with generic and well defined addresses like paths, but we
> have lot of other things to take care of.
>
> I think the general direction is commands that convey their
> purpose via English language verbs are here to stay. Please
> reconsider your vision in the light of this imminent thing.
>
> Thanks,
> Kedar
>
>
>
> Lloyd Chambers wrote:
>> Kedar,
>> Regarding CLI, I am thinking *forward* to a day when we have a CLI
>> that can generically deal with all MBeans via pathnames.
>> As you know, I feel that explicit (hard-coded) commands have their
>> place, but are not a substitute for a CLI that generically
>> supports all objects in the system without the need to invent new
>> commands.
>> Indeed generic support can be easier to use on the whole, as it
>> leverages one common idiom.
>> Lloyd
>> On Mar 24, 2009, at 2:17 PM, Kedar Mhaswade wrote:
>>>
>>>
>>> Lloyd Chambers wrote:
>>>> Pathnames proposal for V3, intended for use in URLs and admin CLI
>>>> is now a separate doc:
>>>> https://glassfish.dev.java.net/nonav/v3/admin/planning/V3Changes/V3_Pathnames.html
>>>
>>> Thanks Lloyd. I will read it carefully.
>>>
>>> I understand "for use in URLs".
>>>
>>> Can you explain what you mean by " for use in admin CLI"? I don't
>>> think set/get/list of "dotted names" is going anywhere. So, how
>>> is admin CLI going to utilize the path names? Are you proposing
>>> new asadmin commands?
>>>
>>> -Kedar
>>>
>>>> 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 <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