Description of problem: Each time I tried to create a datasource through RHQ UI, I got a failure with this error message: java.lang.IllegalArgumentException:item value org.jboss.resource.metadata.mcf.SecurityDeploymentType{[NONE, APPLICATION, DOMAIN, DOMAIN_AND_APPLICATION]}:null for item name securityDeploymentType is not a org.jboss.resource.metadata.mcf.SecurityDeploymentType{[NONE, APPLICATION, DOMAIN, DOMAIN_AND_APPLICATION]} Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Go to an inventoried EAP5 instance 2. Create Child -> Local Tx Datasource 3. Fill in the details with valid data Actual results: creation fails Expected results: datasource created Additional info:
[master 396b849] (http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commitdiff;h=396b849) fixes this. I tested the fix with AS 6.0. QE, please also test it with EAP 5.0 and EAP 5.1.
Ian, Please test yourself with EAP5.0 and 5.1 and if it works, please push to the release branch, and set this to ON-QA
(11:36:57 AM) ccrouch: ips: that bug has not been validated on any version of EAP currently (11:37:12 AM) ccrouch: imho thats not something thats ready for QE (11:37:21 AM) ccrouch: i see your point though (11:37:40 AM) ccrouch: that dev's job is not to test all conceivable versions (11:38:03 AM) ccrouch: so you should test your fix with the latest version of EAP, and make sure it works (11:38:30 AM) ccrouch: QE can then verify it using a different, earlier version of EAP if they wish
Verified my fix against EAP 5.1.1 (successfully created a Datasource child Resource).
Cherry picked fix to release_jon3.x branch - commit a9db32a: http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commitdiff;h=a9db32a
verified with EAP 5.1. attaching screenshot to document the verification of the successful creation of a datasource.
Created attachment 533616 [details] verification screenshot
the fix is specific to EAP 5
This should be verified against EAP 5.0 too.
verified EAP 5.0
marking VERIFIED JON 3 bugs to CLOSED/CURRENTRELEASE
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
*** Bug 816307 has been marked as a duplicate of this bug. ***