Petals ESB Container

Unable to uninstall a component using Ant task after a failed installation

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.1.1
  • Fix Version/s: 3.1.2, 4.0.0
  • Component/s: Ant tasks
  • Security Level: Public
  • Description:
    Hide

    After to have used the Ant task 'jbi-install-component' to install a component with a configuration set as nested element, and containing an invalid parameter name, the installation fails because of the bad parameter name. That is OK.

    But I'm not able to reuse a Ant task to fix my error:

    • I'm not able to uninstall the component because I get the error: "The component 'petals-bc-soap' can not be uninstalled as it is not installed!". That is true.
    • I'm not able to install the component because I get the error: "Other installation package already exists loaded in the component framework: petals-bc-soap"
    Show
    After to have used the Ant task 'jbi-install-component' to install a component with a configuration set as nested element, and containing an invalid parameter name, the installation fails because of the bad parameter name. That is OK. But I'm not able to reuse a Ant task to fix my error:
    • I'm not able to uninstall the component because I get the error: "The component 'petals-bc-soap' can not be uninstalled as it is not installed!". That is true.
    • I'm not able to install the component because I get the error: "Other installation package already exists loaded in the component framework: petals-bc-soap"
  • Environment:
    -

Activity

Hide
Christophe DENEUX added a comment - Tue, 31 May 2011 - 08:49:05 +0200

The source of the problem is the installer that was loaded by the installation task that failed. And the uninstallation task only checks if the component is installed. If the component is not installed but the installer loaded, the uninstallation does nothing.

In my mind and because of symmetry in relation to the installation, the uninstallation task should manages the use case where the component is not installed and the installer loaded, to unload the installer.

Show
Christophe DENEUX added a comment - Tue, 31 May 2011 - 08:49:05 +0200 The source of the problem is the installer that was loaded by the installation task that failed. And the uninstallation task only checks if the component is installed. If the component is not installed but the installer loaded, the uninstallation does nothing. In my mind and because of symmetry in relation to the installation, the uninstallation task should manages the use case where the component is not installed and the installer loaded, to unload the installer.
Hide
Christophe DENEUX added a comment - Tue, 31 May 2011 - 09:02:44 +0200

Note: The Ant task 'jbi-uninstall-component' contains source code to configure the component. Please remove this source code that should remain of a copy/paste from the Ant task 'jbi-install-component'

Show
Christophe DENEUX added a comment - Tue, 31 May 2011 - 09:02:44 +0200 Note: The Ant task 'jbi-uninstall-component' contains source code to configure the component. Please remove this source code that should remain of a copy/paste from the Ant task 'jbi-install-component'
Hide
Christophe DENEUX added a comment - Wed, 1 Jun 2011 - 14:58:54 +0200

Fix in branch petals-entreprise-3.1.x.
A check has been added before to install the component. If the component is not install, unloadInstaller is invoked.

Show
Christophe DENEUX added a comment - Wed, 1 Jun 2011 - 14:58:54 +0200 Fix in branch petals-entreprise-3.1.x. A check has been added before to install the component. If the component is not install, unloadInstaller is invoked.
Hide
Christophe DENEUX added a comment - Wed, 1 Jun 2011 - 14:59:07 +0200

To merge in trunk

Show
Christophe DENEUX added a comment - Wed, 1 Jun 2011 - 14:59:07 +0200 To merge in trunk

People

Dates

  • Created:
    Tue, 31 May 2011 - 08:45:05 +0200
    Updated:
    Mon, 12 Sep 2011 - 17:03:40 +0200
    Resolved:
    Mon, 12 Sep 2011 - 17:03:40 +0200