On Mar 12, 2009, at 3:39 PM, Tim Quinn wrote:
> Kedar,
>
> This seems like a very nice usability enhancement.
> One possible frustration awaits users... If the system is smart
> enough to tell me (as the user) what *I* should do to obtain the
> missing piece, why doesn't it just ask me if I want *it* to do it
> for me?
>
> EJB support is not currently installed. Would you like to
> download and install it now? [y/n]
unfortunately this is not possible through what Kedar is proposing
since the generic deploy command would be the most likely trigger for
that message. But I have to say this would be the most useful
application of the concept "you are missing X, do you want X to be
installed?". Sniffers would be a way to achieve that behaviour (that
was my reason for coming up with Sniffer all together) but some work
is needed to get there.
jerome
>
> I remember with not much fondness a product I used back in the '80s
> called TDMS from Digital (both long gone!). It had a definition
> language in which the word "request" figured prominently. I
> remember with great disgust that, encountering the misspelling
> "reqeust" (I was a frequent offender) its diagnostic error would
> complain something like
>
> Found "reqeust." Did you mean "request?"
>
> Infuriating.
>
> - Tim
>
> Lloyd Chambers wrote:
>> It would be a nice touch.
>>
>> But what is the likelihood of using a command for something that is
>> not installed on the server (perhaps intentionally)...isn't that
>> putting the cart before the horse?
>>
>> Lloyd
>>
>> On Mar 12, 2009, at 3:12 PM, Kedar Mhaswade wrote:
>>
>>> Soliciting inputs from all of you regarding this interesting
>>> problem I am seeing with modular nature of the server.
>>>
>>> The inspiration is drawn from Ubuntu. On my Ubuntu machine, when I
>>> say "svn", it says:
>>>
>>> The program 'svn' is currently not installed. You can install it by
>>> typing:
>>>
>>> sudo apt-get install *subversion*
>>>
>>> Thus, it knows the "intent" of the user and helps him/her to get
>>> there.
>>>
>>> Wouldn't it be nice to have something similar for asadmin especially
>>> since we are in a diverse environments of distributions like web
>>> profile,
>>> full Java EE 6 profile, cluster-aware installation/domain,
>>> or just a domain that's missing certain "capabilities" that might be
>>> available in update center? e.g. you do
>>>
>>> asadmin migrate-timers ... on a domain/installation that has no
>>> EJB support and it comes back and says:
>>>
>>> EJB support is currently not installed. You can install it by typing
>>> pkg install glassfish-v3-ejb (or whatever that is).
>>>
>>> I am tempted to add this as a requirement in CLI spec. What are your
>>> thoughts? If we decide to do this, we need a lot of co-ordination
>>> across
>>> teams to do this.
>>>
>>> Thank you,
>>> Kedar
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>