Branch: refs/heads/jshaughn/as7-deployment Home: https://github.com/rhq-project/rhq Commit: 195b18b45f43f712cedc00d51bfc2ffccc83a38e https://github.com/rhq-project/rhq/commit/195b18b45f43f712cedc00d51bfc2ffccc... Author: Jay Shaughnessy jshaughn@redhat.com Date: 2014-04-30 (Wed, 30 Apr 2014)

Changed paths: M modules/core/client-api/src/main/java/org/rhq/core/clientapi/server/configuration/ConfigurationServerService.java M modules/core/plugin-container/src/main/java/org/rhq/core/pc/inventory/InventoryManager.java M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/configuration/ConfigurationManagerLocal.java M modules/enterprise/server/jar/src/main/java/org/rhq/enterprise/server/configuration/ConfigurationServerServiceImpl.java M modules/plugins/jboss-as-7/src/main/java/org/rhq/modules/plugins/jbossas7/SubsystemDiscovery.java

Log Message: ----------- [1070326] Do not individually track applications with the same WEB Context This is an initial commit for consideration. It enhances discovery in the as7 plugin such that Deployments automatically process versioned artifact names. For example, myapp-1.0.war results in a Deployment resource of myapp.way with version 1.0. A subsequent deployment of myapp-2.0.war results in the existing myapp.war resource being upped to version 2.0.

This is applied to any Deployment based on the SubsystemDiscovery class.

Moreover, general support has been added such that when discovering a new version of an existing resource, not only is the version updated, but the resource's plugin configuration is updated with any properties set by the discovery. In this way if the new version requires updated connection props (like the EAP address path used to connect) it gets updated. Since only those props set by discovery are updated, any existing customizations will be maintained in the existing configuration.