dev@glassfish.java.net

Re: asadmin unistall-addon does not work

From: Sivakumar Thyagarajan <Sivakumar.Thyagarajan_at_Sun.COM>
Date: Mon, 02 Jul 2007 21:58:51 +0530

Hi Manveen

> In my uninstall(..) implementation of my Installer I have added code
> that should delete installer jar and configurator jar.
> On windows, it does not do that. Is this expected?

This sounds similar to the issue
https://glassfish.dev.java.net/issues/show_bug.cgi?id=2287

I would be putting back a fix for this by next week's promotion. Could
you try this with a later build when it is out? Until then, the
workaround in windows, as the bug description says, is "to stop all the
domains and then move the file into .deleted folder."

Thanks
--Siva.

Manveen Kaur wrote:
> Thanks Sreeni,
>
> My understanding is that the install-addon command should remove the
> installer jar from addons directory.
> In my uninstall(..) implementation of my Installer I have added code
> that should delete installer jar and configurator jar.
> On windows, it does not do that. Is this expected?
>
> thanks,
> Manveen
>
>
> Sreenivas Munnangi wrote:
>> Manveen,
>>
>> The command uninstall-addon is expected to uninstall the plugin and
>> for unconfiguring, the procedure you described should work.
>>
>> The uninstall-addon command will cause the method uninstall() to be
>> invoked and the implementation is usually expected to do the inverse
>> of install.
>>
>> I'll be in office on Monday and we can discuss in detail if you have
>> more questions.
>>
>> thanks
>> sreeni
>>
>> Manveen Kaur wrote:
>>
>>> Hi,
>>>
>>> I am unable to undeploy my module using "asadmin uninstall-addon
>>> module" on windows.
>>> I don't see an error message but then nothaing happens. The jars
>>> remain in the addons directory.
>>> Is this a known issue?
>>>
>>> As a workaround I have to
>>> To disable or unconfigure or enable or configure the module
>>> configurator,
>>> edit SDK/domains/domain1/config/domain-registry file and restart the
>>> domain.
>>>
>>> i) To unconfigure Module addon from SDK, then set
>>> module_configurator_${version}.configured=false in domain-registry
>>> file.
>>> module_configurator_${version}.configured=false
>>> module_configurator_${version}.enabled=true
>>>
>>> Restart appserver. This will call unconfigure.
>>>
>>> ii) To configure back (after unconfiguration), set
>>> module_configurator_${version}.configured=true in domain-registry file.
>>> module_configurator_${version}.configured=true
>>> module_configurator_${version}.enabled=true
>>>
>>> Now when you restart, it will redeploy.
>>> Am I missing something here or is this a known problem. If it is, has
>>> this been documented anywhere? Or shall I file a bug against this?
>>>
>>> thanks,
>>> Manveen
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>