[ https://issues.jboss.org/browse/AS7-3347?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky commented on AS7-3347: ---------------------------------------- No, I think it's better to have a jdbc-driver command to deal with them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3347?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3347: ---------------------------------- Summary: JDBC drivers installed via deployment not shown in the management model (was: Datasources installed via deployment not shown in the management model) Description: JDBC drivers installed via deployment are not shown in the management model. I am not quite sure if this is intended or not but I see this as serious usability issue. How is the user supposed to quess the driver name installed via deployment to be able to manage data sources using this driver? [standalone@localhost:9999 /] ls /subsystem=datasources/jdbc-driver h2 [standalone@localhost:9999 /] deploy /usr/share/java/postgresql-jdbc3.jar [standalone@localhost:9999 /] ls /subsystem=datasources/jdbc-driver h2 [standalone@localhost:9999 /] was: Datasources installed via deployment are not shown in the management model. I am not quite sure if this is intended or not but I see this as serious usability issue. How is the user supposed to quess the driver name installed via deployment to be able to manage data sources using this driver? [standalone@localhost:9999 /] ls /subsystem=datasources/jdbc-driver h2 [standalone@localhost:9999 /] deploy /usr/share/java/postgresql-jdbc3.jar [standalone@localhost:9999 /] ls /subsystem=datasources/jdbc-driver h2 [standalone@localhost:9999 /] Updated the issue title and description to reflect that this is about drivers, not datasources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3347?page=com.atlassian.jira.plugin.s... ] Brian Stansberry edited comment on AS7-3347 at 2/6/12 11:31 PM: ---------------------------------------------------------------- Try: [standalone@localhost:9999 /] /subsystem=datasources:installed-drivers-list { "outcome" => "success", "result" => [{ "driver-name" => "h2", "deployment-name" => undefined, "driver-module-name" => "com.h2database.h2", "module-slot" => "main", "driver-datasource-class-name" => "", "driver-xa-datasource-class-name" => "org.h2.jdbcx.JdbcDataSource", "driver-class-name" => "org.h2.Driver", "driver-major-version" => 1, "driver-minor-version" => 3, "jdbc-compliant" => true }] } The example above doesn't have a deployed driver included in the output because the system doesn't have such a driver deployed. But if you had one it should show up as another entry in the list. was (Author: brian.stansberry): Try: [standalone@localhost:9999 /] /subsystem=datasources:installed-drivers-list { "outcome" => "success", "result" => [{ "driver-name" => "h2", "deployment-name" => undefined, "driver-module-name" => "com.h2database.h2", "module-slot" => "main", "driver-datasource-class-name" => "", "driver-xa-datasource-class-name" => "org.h2.jdbcx.JdbcDataSource", "driver-class-name" => "org.h2.Driver", "driver-major-version" => 1, "driver-minor-version" => 3, "jdbc-compliant" => true }] } The example below doesn't have a deployed driver included in the output because the system doesn't have such a driver deployed. But if you had one it should show up as another entry in the list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3347?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3347: ---------------------------------- Issue Type: Feature Request (was: Bug) Changing this to a feature request; it's not a bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3347?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-3347: ------------------------------ Fix Version/s: 7.1.2.Final (was: 7.1.1.Final) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3347?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky resolved AS7-3347. ------------------------------------ Resolution: Won't Fix I've also added tab-completion for driver-name argument in standalone mode, in the case of domain, it's too complicated since the drivers are added per server but the datasources are added per profile. If there are other suggestions, please, let me know. I don't have anything else in mind to add here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3347?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky commented on AS7-3347: ---------------------------------------- No, it wasn't. Ok, I'll add it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira