+++ This bug was initially created as a clone of Bug #852552 +++ Description of problem: For various AS7 subresources, cannot unset resource configuration properties. The properties are updated to any value that is non-empty. The properties however, do not get updated if either the unset checkbox is clicked or if the value from the field is empty. This only applies to non-required properties. For required properties the option to unset the property is not available, and the save button is disable until the field has a non-empty value (UI Validation). How reproducible: Alsways Steps to Reproduce: 1. Discover and import an AS7 standalone server 2. Find any resource with non-required properties that currently set. 3. Either click on the unset checkbox or remove all the contents of the textbox 4. Save the configuration Actual results: The save operation succeeds but the property values is still set to the old value (before unset) Expected results: The save operation succeeds but the property is now null or the default value if a default value is available for the property. Additional info: This bug does not apply to resource creation. If a field is set to unset in the resource creation page, the field will get the default AS7 value upon resource creation since the AS7 plugin will not send a property configuration request to AS7 for the respective property. --- Additional comment from snegrea on 2012-08-29 04:35:07 EDT --- The following resources had to be updated because of this change. There is no functional update to any of these resources. All the changes are done to prevent regressions due to the plugin sending all the properties back to the server. 1) Transport (*/subsystem=infinispan/cache-container=*/transport=TRANSPORT): Removed Transport properties that were no longer in the resource definition. 2) Mod-cluster Configuration (/subsystem=modcluster,mod-cluster-config=configuration): Replaced a property name referenced by alias with the actual name. The alias is no longer working correctly. 3) Distributed Cache (*/subsystem=infinispan/cache-container=*/distributed-cache=*): Created a separate resource for distributed-cache because it has three extra properties when compared to invalidation-cache and replicated-cache. 4) Socket-Binding Group: Update the resource component to avoid sending port-offset configuration to the server for AS7 host controllers by removing the property completely from the definition and update report. Before this change, the property was not sent anyway because it was null, and null values were not sent to the server. 5) Transactions (*/subsystem=transactions): Added special validation rules for properties. 6) Data-source and XA Data-source: Updated the way configuration updates are sent for 9 properties. While these properties look undefined in the server, they cannot undefined or set to null at any point in time. The application server makes use of the default value at all times.
release/jon3.1.x branch commits: http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=f23b9df8bb5de19b72b80635e7adf920993f2945 http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=9aeb0c35d984911e418dbd2d69ebd4ac9e367d4c http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=2e6e37ac2f8ac23b548842c045b67324db10d4a5 http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=0d75b66fd8952290aba7decd717a542dba4ab1ed http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=dd060fd9f2f49693f52a2e073641e23bab5fff78 http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=7ac46f60f75ade6559d420ee19136b5ce542c1cb http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=eab14ccfe45e9618601ac74072ebba2071adccc5
Reverted all the changes added to the release branch and retargeting for 3.1.2.
release/jon3.1.x branch revert commits: http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=6989ac80f94d8b9b1c160dc53a95fe7285889dfd http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=b2cbd93500c879ad560c09340962599543661453 http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=5c8e1a47c9695631e3e244bee3395dad33e5e507 http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=ce6ebd800f079c6dd839b4430610be40181c316d http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=deb31616cdf1dabe5abdbb5bc8539d3b5afe27ea http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=b1ab94bde6140be35d0d94f4770eca861cb181db http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?h=release/jon3.1.x&id=ab0945b268e10612d7af495ef97b8597a73969f8
This, at least superficially, looks related to 844434
Per triage with loleary, crouch, mfoley: Move to JBoss ON product, set target release JON 3.2, clear priority (will be subject to further triage in JON 3.2 timeframe).
This is already in master and the release branch.
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
verified screen-shots attached
Created attachment 924106 [details] before_unset
Created attachment 924107 [details] after_unset
Created attachment 924109 [details] before_unset2
Created attachment 924111 [details] after_unset2