Created attachment 546754 [details] adding datasource - broken UI Version-Release number of selected component (if applicable): Version: 4.3.0-SNAPSHOT Build Number: 35fcafb How reproducible:always Steps to Reproduce: 1. have as7 standalone (I have eap6 DR8) 2. create deployment child using RHQ UI (hello.war) 3. wait for agent to discover deployment 4. try to add datasource using RHQ UI Actual results: I am not able to fill all required fields when adding datasource, instead of 'Driver Name:' input field there is radio with the name of deployment (hello.war), see screenshot Expected results: Driver name field is available Additional info:
Did you upload a valid driver first? You need to go to the server, add a driver as deployment and then go to the datasources to create the datasource. But I agree, that .war files should not show up in that list.
No, I don't add driver, I am creating datasource with same driver as the exampleDS, so I use h2 driver
master 4073cfff18630 filters for .jar files as drivers, so deployed .war and .ear should no longer show. Question is how to deal with module loaded drivers - h2 is (afaik) supposed to go away in EAP6. One could allow an additional text field where such a driver name can be entered by hand. The list of deployed jars would then be optional.
Add text field for naming the driver. If neither selected driver nor text field or both are present, throw an Exception in code.
We put this on QA, as the original task is done. and open a new RfE for support of module loaded drivers
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.