Branch: refs/heads/master Home: https://github.com/rhq-project/rhq Commit: 98bde1c66b3bc78b6907531688fdb7fdd63edc8a https://github.com/rhq-project/rhq/commit/98bde1c66b3bc78b6907531688fdb7f... Author: Libor Zoubek <lzoubek(a)redhat.com&gt; Date: 2014-05-27 (Tue, 27 May 2014) Changed paths: M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/BaseComponent.java M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/DomainDeploymentComponent.java A modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/DomainDeploymentDiscovery.java M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/HostControllerComponent.java M modules/plugins/jboss-as-7/src/main/resources/META-INF/rhq-plugin.xml Log Message: ----------- [BZ 1069691] (JON3-25, PRODMGT-368) DomainDeployments should be managed in a single menu option in domain mode Deploymet resource has been removed from Server-Group level. Now we have only DomainDeployment (living under DC) and Deployment (discovered under ManagedServer). We manage everything related to ServerGroups within DomainDeployment's configuration and operations. Operation 'promote' remains (although not needed anymore) To assign DomainDeployment with Server-Group user adds new Configuration map item, select SG, runtime-name and enabled/disabled state. To enable/disable deployment on given SG user edits particular configite and changes enabled boolean attribute To remove DomainDeployment from SG user just removes given map item. Given domain deployment cannot be assigned to same server group more than once (even with different runtime-name) - EAP restriction. runtime-name cannot be changed on existing map items (it's documented and ignored) New operation for DomainDeployment resource called 'restart' was introduced. User can restart deployment in particular SG or in all assigned SGs. DomainDeplooyment's getAvailability() was also changed to return MISSING instead of DOWN when deployment is not found on EAP. DomainDeployments get discovered only under master DomainController, not slave HostControllers Commit: bf2f036d4049dcc5b5d35fe6015f82acf2f2f61d https://github.com/rhq-project/rhq/commit/bf2f036d4049dcc5b5d35fe6015f82a... Author: Libor Zoubek <lzoubek(a)redhat.com&gt; Date: 2014-05-30 (Fri, 30 May 2014) Changed paths: M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/BaseServerComponent.java M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/HostControllerComponent.java Log Message: ----------- on HosctController component hold info if given HC is DC as well This value is updated on component start and also by availability code, when going from DOWN to UP (to handle cases, when HC was reconfigured to DC) Access to HC Component property is synchronized, because value is updated by avail code and can read by discovery code Commit: d3c6251b5f8aebf1ad4c24b703e3f1adffe338eb https://github.com/rhq-project/rhq/commit/d3c6251b5f8aebf1ad4c24b703e3f1a... Author: Heiko W. Rupp <hwr(a)pilhuhn.de&gt; Date: 2014-05-30 (Fri, 30 May 2014) Changed paths: M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/BaseComponent.java M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/BaseServerComponent.java M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/DomainDeploymentComponent.java A modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/DomainDeploymentDiscovery.java M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/HostControllerComponent.java M modules/plugins/jboss-as-7/src/main/resources/META-INF/rhq-plugin.xml Log Message: ----------- Merge pull request #40 from lzoubek/feature/JON3-25 [BZ 1069691] (JON3-25, PRODMGT-368) DomainDeployments should be managed in a single menu option in domain mode Compare: https://github.com/rhq-project/rhq/compare/bd90bfa78c36...d3c6251b5f8a