Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-5029

server group deployment resource doesn't include correct "mananged" value

    Details

    • Steps to Reproduce:
      Hide

      Execute an unmanaged deployment in a fresh EAP 7.3.1 zip installation running in Domain mode.

      [domain@localhost:9990 deployment] deploy /Development/Workspaces/eap-quickstarts/jboss-eap-7.3.0.GA-quickstarts/greeter/target/greeter.war --all-server-groups --unmanaged
      

      After the deployment, check the following Management Console: Deployment --> Server Groups --> main-server-group --> greeter.war --> Enabled, Managed, Exploded

      Show
      Execute an unmanaged deployment in a fresh EAP 7.3.1 zip installation running in Domain mode. [domain@localhost:9990 deployment] deploy /Development/Workspaces/eap-quickstarts/jboss-eap-7.3.0.GA-quickstarts/greeter/target/greeter.war --all-server-groups --unmanaged After the deployment, check the following Management Console: Deployment --> Server Groups --> main-server-group --> greeter.war --> Enabled, Managed, Exploded

      Description

      Unmanaged deploys show a checkmark that they are "managed" if you view the deployment under Server Groups. The deployment does however show correctly that it is un-managed in the Content Repository section.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  soul2zimate Chao Wang
                  Reporter:
                  soul2zimate Chao Wang
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: