Hi Kedar,
See below...
Kedar Mhaswade wrote:
> I am not sure I understand.
>
> If the update tool client is designed to get the latest updates
> of admin GUI from the repo, when s/he downloads it, I am sure it is
> an IPS
> package. But the user has already said that s/he wants the new
> admin GUI, why does s/he have to do that on admin GUI again?
That would not happen. If they have a newer version downloaded from the
UC already, it will automatically install it.
> Isn't the only step remaining -- expanding the IPS package to get the
> directory layout of the admin GUI app?
>
> I'd suggest keeping AdminConsoleAdapter out of update logic.
We can keep the adapter out of the part where we ask if they want to do
any update, but we cannot keep the upgrade process out of the adapter --
there's nothing else that can do the upgrade. Prompting the user on
first access is done by FF and other applications so I think it's a nice
ease-of-use feature... but we could skip it.
I think Anissa's "case 3" was described in a way that wasn't clear.
Case 3 is when the user has NOT downloaded it from UC (case 1 and 2).
In case 3, on first access we can check for the user to see if an update
is available and install it before they access the admin console
(although this may still require a restart, unfortunately). In this
case, the user would be prompted w/ a screen like the original screen
asking for permission to install... and that would be the *only* prompt
they get for the upgrade.
Ken
> -Kedar
>
> Anissa Lam wrote:
>> Kedar Mhaswade wrote:
>>>> - admin console upgrade
>>>
>>> Is there a description of what this means? Can you point me to
>>> a write-up somewhere?
>> Here is the description: Admin Console need to support the case of
>> updating the console itself. There are 3 update scenario:
>> 1. user get the update from updatetool
>> 2. when running console, download the new version of admin console
>> For both cases above, upon server restart, we detect the case and
>> redeploy the console before loading it.
>>
>> 3. when server restart, we detect that new update for admin
>> console is available, and inform the user.
>> If user decides to download this new version, they can but they need
>> to restart the server again to see this changes. This restart is
>> mandatory, since we redeploy the new war, and some of the new jars
>> that comes with the IPS package is under the modules directory.
>> Since the previous version of these jars are already loaded, in
>> order to sync up, user needs to restart the server.
>>
>> I will update the one pager to include the above description.
>>>> - Application Management
>>>
>>> This is the deployment descriptor editing part, right?
>> yes.
>>> Let's call/document it as such so that users don't misunderstand it.
>> Thats what the feature called. I will ensure that doc team knows
>> thats what it is about. I believe they already does.
>>
>> thanks
>> Anissa.
>>>
>>> Thanks,
>>> Kedar
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>