Petals ESB Container

The error message of Ant task 'jbi-uninstall-component' is not clear when the component is not installed

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • 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

    When the Ant task 'jbi-uninstall-component' is used to uninstall a component that was not installed previously (no component installer was loaded), the error message is not clear: "ObjectName must not be null".

    Replace it by something like: "The component '<component-name>' does not exist." where <component-name is the component JBI identifier.

    Show
    When the Ant task 'jbi-uninstall-component' is used to uninstall a component that was not installed previously (no component installer was loaded), the error message is not clear: "ObjectName must not be null". Replace it by something like: "The component '<component-name>' does not exist." where <component-name is the component JBI identifier.
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Christophe DENEUX made changes - Wed, 8 Jun 2011 - 10:55:20 +0200
Field Original Value New Value
Summary The error message of 'jbi-uninstall-component' is not clear when the component is not installed The error message of Ant tasks managing component lifecycle is not clear when the component is not installed
Priority Blocker [ 1 ]
Description When the Ant task 'jbi-uninstall-component' is used to uninstall a component that was not installed previously, the error message is not clear: "ObjectName must not be null". When the Ant task 'jbi-start-component', 'jbi-stop-component', 'jbi-shutdown-component' or 'jbi-uninstall-component' is used to change the state of a component that was not installed previously (no component installer was loaded), the error message is not clear: "ObjectName must not be null".

Replace it by something like: "The component '<component-name>' does not exist." where <component-name is the component JBI identifier.
Christophe DENEUX made changes - Fri, 10 Jun 2011 - 16:21:43 +0200
Priority Blocker [ 1 ] Minor [ 4 ]
Component/s Ant tasks [ 10202 ]
Component/s Installation/Deployment [ 10041 ]
Christophe DENEUX made changes - Thu, 16 Jun 2011 - 09:03:34 +0200
Status New [ 10000 ] Open [ 10002 ]
Assignee Roland Naudin [ rnaudin ] Christophe DENEUX [ cdeneux ]
Christophe DENEUX made changes - Thu, 16 Jun 2011 - 09:03:36 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Christophe DENEUX made changes - Thu, 16 Jun 2011 - 11:31:54 +0200
Summary The error message of Ant tasks managing component lifecycle is not clear when the component is not installed The error message of Ant task 'jbi-uninstall-component' is not clear when the component is not installed
Description When the Ant task 'jbi-start-component', 'jbi-stop-component', 'jbi-shutdown-component' or 'jbi-uninstall-component' is used to change the state of a component that was not installed previously (no component installer was loaded), the error message is not clear: "ObjectName must not be null".

Replace it by something like: "The component '<component-name>' does not exist." where <component-name is the component JBI identifier. 		When the Ant task 'jbi-uninstall-component' is used to uninstall a component that was not installed previously (no component installer was loaded), the error message is not clear: "ObjectName must not be null".

Replace it by something like: "The component '<component-name>' does not exist." where <component-name is the component JBI identifier.
Christophe DENEUX made changes - Thu, 16 Jun 2011 - 11:45:54 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 3.1.2 [ 10156 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 16 Jun 2011 - 11:46:07 +0200
Status Resolved [ 10004 ] Open [ 10002 ]
Resolution Fixed [ 1 ]
Mathieu Carrolle made changes - Tue, 13 Sep 2011 - 11:46:07 +0200
Assignee Christophe DENEUX [ cdeneux ] Mathieu Carrolle [ mcarrolle ]
Mathieu Carrolle made changes - Tue, 13 Sep 2011 - 11:46:10 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Mathieu Carrolle made changes - Tue, 13 Sep 2011 - 11:46:15 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 4.0.0 [ 10108 ]
Resolution Fixed [ 1 ]

People

Dates

  • Created:
    Wed, 1 Jun 2011 - 20:09:06 +0200
    Updated:
    Tue, 13 Sep 2011 - 11:46:15 +0200
    Resolved:
    Tue, 13 Sep 2011 - 11:46:15 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.