glassfish
  1. glassfish
  2. GLASSFISH-14216

Clustered Instances page: disable start/stop appropriately

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Trivial Trivial
    • Resolution: Unresolved
    • Affects Version/s: 3.1
    • Fix Version/s: future release
    • Component/s: admin_gui
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      14,216

      Description

      build: glassfish-3.1-b25-10_21_2010.zip

      Start/stop buttons on Clustered Server Instances page should not be always
      enabled. Currently, when clustered server is running, when I select that
      instance in the table, both start and stop buttons are enabled for that
      instance. Only stop button should be enabled for a running instance and only
      start button should be enabled for a stopped instance.

        Activity

        Hide
        lidiam added a comment -

        Created an attachment (id=5238)
        screenshot

        Show
        lidiam added a comment - Created an attachment (id=5238) screenshot
        Hide
        Anissa Lam added a comment -

        The table may contain more than 1 instance and they can be running or stopped. User can select
        more than 1 instance and they can be at different state, in that case, which button should be
        enabled ?
        The table shows clearly whether the instance is running or not, and we don't see the need to
        special case when there is only 1 instance.
        Besides, if the instance is already running, it will just return.
        This is also the behavior for enable or disable resource or application. This is the same behavior as
        in v2. closing as will not fix.

        Show
        Anissa Lam added a comment - The table may contain more than 1 instance and they can be running or stopped. User can select more than 1 instance and they can be at different state, in that case, which button should be enabled ? The table shows clearly whether the instance is running or not, and we don't see the need to special case when there is only 1 instance. Besides, if the instance is already running, it will just return. This is also the behavior for enable or disable resource or application. This is the same behavior as in v2. closing as will not fix.
        Hide
        lidiam added a comment -

        Ideally GUI should not display start button as enabled if there are no instances
        to start. The same goes for stop - if all instances in the table are stopped
        this button should be disabled. I'm changing this issue to enhancement request.

        Show
        lidiam added a comment - Ideally GUI should not display start button as enabled if there are no instances to start. The same goes for stop - if all instances in the table are stopped this button should be disabled. I'm changing this issue to enhancement request.
        Hide
        Anissa Lam added a comment -

        target for future release

        Show
        Anissa Lam added a comment - target for future release

          People

          • Assignee:
            Anissa Lam
            Reporter:
            lidiam
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: