Kedar,
Having users re-enter data that is not necessary (because they have
already given that data to the server) is a flaw. It lowers the
usability of the CLI.
Jerome identified that flaw and implemented a new command (redeploy) to
help eliminate it. Since Jerome is an 'architect', one of his charters
is to identify flaws in the current product and design solutions to
them, before the user community has filed issues about them.
He had done his job... and then it seems that his work got undone... for
reasons which seem to focus on "our" (Project GlassFish developers)
convenience and not user convenience.
Note: Our convenience may be a valid reason to defer implementation, if
the solution that Jerome was proposing were just at the design stage.
vbk
Kedar Mhaswade wrote:
> Hmmm. I must not be reading those.
> In V2, we don't have an *asadmin redeploy* command and no
> user has reported this to be a flaw. Why would we want users
> to undergo deploy/redeploy/undeploy when deploy/undeploy worked?
>
> Again, I am talking only w.r.t. "asadmin".
>
> Jerome Dochez wrote:
>> Independently of the --force fate, I think a redeploy command is
>> highly desirable as it comes quite naturally to Java EE users
>> accustomed to deploy/redeploy/undeploy actions as specified
>> everywhere in industry standard docs, books and postings.
>>
>> Jerome
>>
>> On Mar 13, 2008, at 9:41 AM, Kedar Mhaswade wrote:
>>
>>> I thought that the plan of record is till we find the correct
>>> default value
>>> for --force, it remains true. This was after ccc meeting yesterday.
>>>
>>> Thus, asadmin deploy foo.war [foodir] followed by asadmin deploy
>>> foo.war
>>> [foodir] should result in redeployment of the underlying
>>> application/module.
>>>
>>> This means, we should not use "redeploy" command just yet, as "deploy
>>> over deploy" is supposed to achieve the same effect.
>>>
>>> I am not convinced we ought to have a "redeploy" command.
>>>
>>> Jerome, Bill, please help clarify doubts here.
>>>
>>> - Kedar
>>>